Hi everyone, it seems sprints in Jira are globally visible (across projects), and, when editing an issue, provide little context as to what that sprint is.
I think some sort of prefix in names should be adopted by everyone using sprints in Jira -- basically James D right now -- to make it easy to see what it relates to. "1.1" is just too light on context. In James' case, BO, Blue Ocean, or similar would be helpful. In SECURITY related "sprints" (not really, but still helps plan) I've started using the 'SECURITY' prefix for sprints. So, for example, the 'sprint' released on Feb 1 was "SECURITY: Collins". WDYT? Daniel -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/51EB3A86-FDC6-452D-A3B5-2996865B9BF9%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
