Naming convention for sprints in Jira

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

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

--
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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

Re: Naming convention for sprints in Jira

James Dumay
SGTM

On Tue, Mar 14, 2017 at 6:05 AM Daniel Beck <[hidden email]> 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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAErbOvSZqeudFLcc8Ehh4WVVVpoGVAGUdT42KjOzo4eOniaMXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Naming convention for sprints in Jira

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

On Tue, Mar 14, 2017 at 7:48 AM James Dumay <[hidden email]> wrote:
SGTM

On Tue, Mar 14, 2017 at 6:05 AM Daniel Beck <[hidden email]> 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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

Re: Naming convention for sprints in Jira

stephenconnolly
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

On 13 March 2017 at 20:54, James Dumay <[hidden email]> 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...)

On Tue, Mar 14, 2017 at 7:48 AM James Dumay <[hidden email]> wrote:
SGTM

On Tue, Mar 14, 2017 at 6:05 AM Daniel Beck <[hidden email]> 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 [hidden email].
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.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMyS_LGXtj%2B4PbpKTP9CygnFUG5qduDLw321wrsduFkAzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Naming convention for sprints in Jira

Daniel Beck
In reply to this post by James Dumay

> On 13.03.2017, at 21:54, James Dumay <[hidden email]> 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.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C76D1B1A-4E2D-4BF4-A407-A21EE4822D7E%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Naming convention for sprints in Jira

Kanstantsin Shautsou-2
In reply to this post by stephenconnolly
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. 

On Tuesday, March 14, 2017 at 12:07:47 AM UTC+3, Stephen Connolly wrote:
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

On 13 March 2017 at 20:54, James Dumay <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="3OkkxMJ8DwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jdu...@...> 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...)

On Tue, Mar 14, 2017 at 7:48 AM James Dumay <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="3OkkxMJ8DwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jdu...@...> wrote:
SGTM

On Tue, Mar 14, 2017 at 6:05 AM Daniel Beck <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="3OkkxMJ8DwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">m...@...> 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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="3OkkxMJ8DwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAErbOvSCb04K-2_K8q3DdfnGhX9YgqzCayd-mNz4cZpMCL%3DpXg%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAErbOvSCb04K-2_K8q3DdfnGhX9YgqzCayd-mNz4cZpMCL%3DpXg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAErbOvSCb04K-2_K8q3DdfnGhX9YgqzCayd-mNz4cZpMCL%3DpXg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAErbOvSCb04K-2_K8q3DdfnGhX9YgqzCayd-mNz4cZpMCL%3DpXg%40mail.gmail.com.

For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8753eedf-092f-4b05-85cf-ce382f7b927d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Naming convention for sprints in Jira

Daniel Beck

> On 15.03.2017, at 17:39, Kanstantsin Shautsou <[hidden email]> wrote:
>
> Now it messed with statuses created for somebody needs.

What are you referring to?

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C2873E87-86BC-4188-BABB-435961B1E09C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Naming convention for sprints in Jira

Kanstantsin Shautsou-2
Triangle and etc, or it finally removed?

On Wednesday, March 15, 2017 at 7:54:52 PM UTC+3, Daniel Beck wrote:

> On 15.03.2017, at 17:39, Kanstantsin Shautsou <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="L2YmuB4MEAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">kanstan...@...> wrote:
>
> Now it messed with statuses created for somebody needs.

What are you referring to?

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20a463aa-d874-49a8-9ef5-e8f42bcbc0cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Naming convention for sprints in Jira

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 написал:
Triangle and etc, or it finally removed?

On Wednesday, March 15, 2017 at 7:54:52 PM UTC+3, Daniel Beck wrote:

> On 15.03.2017, at 17:39, Kanstantsin Shautsou <[hidden email]> wrote:
>
> Now it messed with statuses created for somebody needs.

What are you referring to?

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/83f2724c-b327-495c-91a5-7b1e60aaed95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.