|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-15562) Support setting the... [email protected] (JIRA)
- [JIRA] (JENKINS-15562) Support settin... [email protected] (JIRA)
- [JIRA] (JENKINS-15562) Support settin... [email protected] (JIRA)
- [JIRA] (JENKINS-15562) Support settin... [email protected] (JIRA)
- [JIRA] (JENKINS-15562) Support settin... [email protected] (JIRA)
- [JIRA] (JENKINS-15562) Support settin... [email protected] (JIRA)
- [JIRA] (JENKINS-15562) Support settin... [email protected] (JIRA)
- [JIRA] (JENKINS-15562) Support settin... [email protected] (JIRA)
- [JIRA] (JENKINS-15562) Support settin... [email protected] (JIRA)
- [JIRA] (JENKINS-15562) Support settin... [email protected] (JIRA)
- [JIRA] (JENKINS-15562) Support settin... [email protected] (JIRA)

I see that there is a use case, but I don't see that this use case is critical to have. We could have all kind of data - even dynamic information - included in the 'default' version.
There are - for my taste - even too many option in the Advanced section, already.
So again my question: would a default version be enough?