I noticed non-sequencial story reference# such as
66784,65785,... with no scrum business value. It would be
preferable to have this preceded with the Epic (aka milestone) and
the sprint #, as in Epic #5 Sprint #2 Story
#66784.
Support Staff2 Posted by Rodney on 03 Mar, 2010 09:26 PM
Where are you referring to this? On story edit? Or on the
tooltips? The thing is you already know which sprint you are in
because you are hovering within a sprint. The link on story edit
can be used as a url you can give someone else to access the story.
They do have to have permission to view the project, of course.
I'm talking about the tooltip which shows the reference #. It
would be useful when coordinating across multiple sprints/epics to
see the prefixed references.
Yes, API is for system usage and I understand that.
I'm speaking of the reference value displayed to end-users such
as myself. While you may trivialize this point, there should be a
display value that I can easily recognize, sequential for my
project and independent of other projects. Believe me, when it
comes to history and tracking purpose, this is valuable.
Support Staff7 Posted by Rodney on 04 Mar, 2010 10:07 PM
The part that I'm not seeing is that whenever you hover over a
story, you already are in the context of a sprint. So, why would it
be valuable to see the same information twice?
Support Staff 2 Posted by Rodney on 03 Mar, 2010 09:26 PM
Where are you referring to this? On story edit? Or on the tooltips? The thing is you already know which sprint you are in because you are hovering within a sprint. The link on story edit can be used as a url you can give someone else to access the story. They do have to have permission to view the project, of course.
3 Posted by Quentin on 03 Mar, 2010 10:36 PM
I'm talking about the tooltip which shows the reference #. It would be useful when coordinating across multiple sprints/epics to see the prefixed references.
4 Posted by Quentin on 04 Mar, 2010 05:12 PM
Also, the ref# appears on Stories and Tasks.
Support Staff 5 Posted by David on 04 Mar, 2010 08:37 PM
The primary purpose of this is to give a handle for using the API. We may add more info when we support milestones (aka epics)
David resolved this discussion on 04 Mar, 2010 08:37 PM.
Quentin re-opened this discussion on 04 Mar, 2010 09:53 PM
6 Posted by Quentin on 04 Mar, 2010 09:53 PM
Yes, API is for system usage and I understand that.
I'm speaking of the reference value displayed to end-users such as myself. While you may trivialize this point, there should be a display value that I can easily recognize, sequential for my project and independent of other projects. Believe me, when it comes to history and tracking purpose, this is valuable.
Support Staff 7 Posted by Rodney on 04 Mar, 2010 10:07 PM
The part that I'm not seeing is that whenever you hover over a story, you already are in the context of a sprint. So, why would it be valuable to see the same information twice?
Rodney resolved this discussion on 04 Mar, 2010 10:07 PM.
Quentin re-opened this discussion on 04 Mar, 2010 10:37 PM
8 Posted by Quentin on 04 Mar, 2010 10:37 PM
Agreed. Value would only come from history.
Anyhow, compared to the lack of Capacity Planning, I see this as a minor change.
Rodney resolved this discussion on 04 Mar, 2010 11:40 PM.