Naming convention for sprints in Jira

[Daniel Beck]

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]

SGTM

--

James Dumay

Product Manager

CloudBees, Inc.

Skype: jdumaycb Twitter: i386

[James Dumay]

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...)

[Stephen Connolly]

Yeah but then we'd have lots of fun as the same issue moves through 1000's of products because the user didn't know which one to file in

--
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 jenkinsci-dev+unsubscribe@googlegroups.com.
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.

[Daniel Beck]

> On 13.03.2017, at 21:54, James Dumay <jdu...@cloudbees.com> wrote:
>
> 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...)

SECURITY does and I still see a list of your sprints in JENKINS when I edit SECURITY issues.

[Kanstantsin Shautsou]

The best way for maintainer is not to use jenkins JIRA at all. Now it messed with statuses created for somebody needs. While in GH issues you have only list of issues and PRs related to code. 

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

[Daniel Beck]

> On 15.03.2017, at 17:39, Kanstantsin Shautsou <kanstan...@gmail.com> wrote:
>
> Now it messed with statuses created for somebody needs.

What are you referring to?

[Kanstantsin Shautsou]

Triangle and etc, or it finally removed?

[Oleg Nenashev]

Which project in JIRA do you mean? I do not recall such statuses in the JENKINS project. If you mean labels, than it is a separate story.

среда, 15 марта 2017 г., 22:03:51 UTC+1 пользователь Kanstantsin Shautsou написал: