-
Suggestion
-
Resolution: Duplicate
-
None
-
None
The new Sprint field used by the Rapid board, separate from the Fix For Version, is great.
However right now a big flaw with using it is that there is no convenient way to set it directly from the Edit Issue view (as opposed to using the Plan tab UI of the Rapid Board). This is often necessary - say there is a critical bug that needs to be filed and added to the current sprint, it would be nice to do it in a single shot rather than having to create it, find it on the rapid board and drag it into the sprint.
You can add the Sprint field to the Default issue screen, which makes it appear when Editing the issue, but this shows a text field where you have to enter the ID of the sprint. Since this is a system-level value that no user would ever know, its less than useful to non-power users.
The ideal would be to enable the use of either a Select dropdown or an autocomplete-type editor a la fix for versions. I suspect this shouldn't be too hard to do, just allow the Autocomplete/Select renderer for the Sprint field.
If there is any workaround to get this working before it's released (say some sample plugin code) that could be posted this would be great.
- duplicates
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-5213] Enable Select or Autocomplete Renderer for new Greenhopper Sprint field
Mattias Jiderhamn
added a comment - This is a major issue for us, and will have us consider going back to the classic boards
Mattias Jiderhamn
added a comment - This is a major issue for us, and will have us consider going back to the classic boards Obviously using the sprint field instead of sub-versions is the new proposed way of handling the sprint information - and I do support keeping release version and sprint separate. This means that it is necessary to show this information on the main issue screen so people see the release version and the sprint the issue worked on.
However this automatically creates an editable field which has the above mentioned problem with editing usability. My opinion is:
- Either the field is not editable - neither on the issue screen nor on the edit masks - and only editable using the rapid board
- Or (preferred) it is editable in a useful way, that is, using a list or autocomplete as suggested above.
Dan Kokotov
added a comment - Shaun,
Thanks for the quick response! I understand about the historical sprints - however this is just saying the value of the Sprint field is a list of ids (effectively). In this way it's analogous to fix version (where in fact sprints used to be stored) - so why not allow an autocomplete renderer that allows selection of multiple sprints in the same way as you can select multiple versions for Fix Version?
Generally dragging it in works, but for when you know its going into the sprint its kind of a pain. Especially if the backlog is of more than trivial size - since the new issue goes to the bottom, so dragging it to the top takes some time.
Another use case is when you want to move an issue out of the sprint - currently (as far as i can tell) there is no good way of doing that once you adopt Rapid Board/the separate Sprint field.
The sprint field can already made editable by modifying the configuration of its custom field appropriately (though most users probably won't do that), but without being able to use the autocomplete/select renderer with it its only useful to a power user. I'm hoping its not complex to make it so the sprint field is eligible for those renderers, and you'd consider doing this - so ven if you don't plan to by default make the Sprint field editable, it would be doable for folks who find that useful.
Thanks!
Dan Kokotov
added a comment - Shaun,
Thanks for the quick response! I understand about the historical sprints - however this is just saying the value of the Sprint field is a list of ids (effectively). In this way it's analogous to fix version (where in fact sprints used to be stored) - so why not allow an autocomplete renderer that allows selection of multiple sprints in the same way as you can select multiple versions for Fix Version?
Generally dragging it in works, but for when you know its going into the sprint its kind of a pain. Especially if the backlog is of more than trivial size - since the new issue goes to the bottom, so dragging it to the top takes some time.
Another use case is when you want to move an issue out of the sprint - currently (as far as i can tell) there is no good way of doing that once you adopt Rapid Board/the separate Sprint field.
The sprint field can already made editable by modifying the configuration of its custom field appropriately (though most users probably won't do that), but without being able to use the autocomplete/select renderer with it its only useful to a power user. I'm hoping its not complex to make it so the sprint field is eligible for those renderers, and you'd consider doing this - so ven if you don't plan to by default make the Sprint field editable, it would be doable for folks who find that useful.
Thanks! Hi Dan,
We don't plan on making the Sprint field editable because it contains more than just the current Sprint the issue is part of (it also contains historical information about which Sprints the issue has passed through).
You should not directly edit the Sprint field.
We'd recommend adding the critical bug while you're in the Rapid Board plan mode then dragging it in.
Good news! This issue has been resolved in the latest version of JIRA Agile. Please see the linked issue for more information.
Regards,
JIRA Agile Team