Though this is one of those situations where if we used JIRA correctly (anything having its own lifecycle should have a project) we could avoid the name spacing issues (with the added bonus of being able to use Release Versions - no more confusion as to what has shipped or not...)
On Tue, Mar 14, 2017 at 7:48 AM James Dumay <[email protected]> wrote: > SGTM > > On Tue, Mar 14, 2017 at 6:05 AM Daniel Beck <[email protected]> wrote: > > 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 > > -- > James Dumay > Product Manager > CloudBees, Inc. > Skype: jdumaycb Twitter: i386 > -- James Dumay Product Manager CloudBees, Inc. Skype: jdumaycb Twitter: i386 -- 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/CAErbOvSCb04K-2_K8q3DdfnGhX9YgqzCayd-mNz4cZpMCL%3DpXg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
