[FOLIO-1472] Implement rational sort order for JIRA links Created: 06/Sep/18 Updated: 12/Nov/18 Resolved: 06/Sep/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Story | Priority: | P3 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint46 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
| Sprint: |
| Description |
|
Purpose: to order the links in JIRA work items in a predictable manner. Right now they seem completely random and are hard to make sense of (see attached screenshot of current situation). Holly Mistlebauer says there should be an advanced setting called jira.view.issue.links.sort.order Could we set that to Issue type then Issue key? That way they would be organized by type (e.g. stories, bugs) and then sorted by the order in which they were created. Ideally this would apply to both "Issues in epic" (for epics) and "Issue links" (for all issues). |
| Comments |
| Comment by Cate Boerema (Inactive) [ 06/Sep/18 ] |
| Comment by John Malconian [ 06/Sep/18 ] |
|
ok. I've reconfigured the sort order by type and then by key. ('type, key'). Please verify that this is working the way you want it. Hopefully, it's retroactive to existing issues. |
| Comment by Ann-Marie Breaux (Inactive) [ 06/Sep/18 ] |
|
Hi John Malconian Thank you! The Issue Links definitely are showing up in Key order now, but that seems to be the primary sort, not the issue type. And it's definitely retroactive. Here's the new display from UXPROD-47: The "issues in Epic" have not changed (see second screenshot) - maybe there is another setting that controls them? If you want to check the effects of the settings changes,
|
| Comment by John Malconian [ 06/Sep/18 ] |
|
It appears that when specifying 'type' and then 'key', 'type' is sorted per project (or something like that). Not exactly what we wanted or were expecting. This config option does not apply to sorting epic issues. There is no configuration option for that. There may be some workarounds that can be tried here: I think I have taken this about as far as I can go with it. |
| Comment by Cate Boerema (Inactive) [ 06/Sep/18 ] |
|
Ann-Marie Breaux, given this, do you think it would be better to sort just by key? I don't feel that strongly about sorting by type first, especially if it's not working the way we expected. |
| Comment by Ann-Marie Breaux (Inactive) [ 06/Sep/18 ] |
|
Hi Cate Boerema Seems like key only (no type) would be best then. John Malconian do you mind making that one tweak? And then we can button this one up. Any little tweaks like this that can make the Jira screen more logical are really helpful, so thank you for poking around on this! |
| Comment by John Malconian [ 06/Sep/18 ] |
|
ok. all set. not much of a difference after removing 'type' however since it didn't exactly do what he expected to begin with. |
| Comment by Ann-Marie Breaux (Inactive) [ 06/Sep/18 ] |
|
Key order is fine. Thank you!! |
| Comment by Ann-Marie Breaux (Inactive) [ 06/Sep/18 ] |
|
Thanks also for the link to the community discussion of Issues in Epic. I was able to get them sequenced by copying the Features kanban board, filtering to just the features in the Batch Loader epic, and then dragging and dropping to get them in numeric order within each status category. Not very elegant, but it worked. |