@LironThank you, and thanks for replying on that thread I linked, for some reason the Reply field isn't working properly on some pages - the grey "Reply..." text stays and the box doesn't update to a submittable text box. But this one did for some reason? Anyway I just wanted to acknowledge your response and maybe bring this reply issue to your attention.
@Liron we are using Jira Software, standard plan in our organization and I am unable to see these usability improvements on our company managed project. Is this available for everyone?
Thank you for the feedback. Something you might find useful is our Bulk rank feature. It's not as simple as drag-and-drop, but you can select a family of issues and bulk rank the entire selection.
The best way to do this for the entire hierarchy is:
Use the issue's meatball menu to "select this and all descendant issues"
Select the "Bulk actions" dropdown
Select "Rank"
Then you can chose where you want to rank the entire selection. Either to the Top, Bottom or above/below another specific issue's rank
@Rhys Christian Thank you for your answer. I know this option and I use it as a workaround, but it has a significant issue that caused several hard to identify problems in my workflow. Let me explain.
When you schedule a plan, naturally only issues with the estimate are scheduled. Their parents are just wrapped around them. This means that only the level with the estimates (story level most of the time) influences the plan.
The result of the above is that ranks of epics and other higher levels that don't have an estimate are not always at the same place as their children.
So now, when the user wants to use your workaround, it would be a mistake to rank the selection above/below an issue on that high level, as it can be anywhere as is not "glued" to the ranks of its underlying stories with estimates.
To really be sure that you do what you intend to do, you need to do the following:
Find a high level issue above/below which you want to rank your issue.
Expand it to the level with estimates.
If you want to rank above it, find the highest ranked children of that high level story that has an estimate, or, if you want to rank below, find the lowest one.
Provide that issue's key to the rank above/below prompt instead of the high level key.
As you can see, it's cumbersome but it's the only way to make sure you're ranking things correctly.
The old approach from Portfolio 2.0 was better, because thanks to it high level issues were "glued" to their children and you could safely, easily and quickly manipulate the plan only on the high level and it worked flawlessly, without surprises.
And finally, I need to underline again: what's to point of how it is implemented right now? It's extremely misleading. Is there a plan manager who wants to move high level items without having an effect of the actual work plan? I don't understand why anyone would want that. If something is made important on the high level and moved high in the plan, we want the stories to move higher for the developers too.
Finally, I need to add, that I'm currently mailing with a Jira representative who responded to my feedback about it. He was also misled by it and thought that if you rerank a high level story it's children are also reranked because they are visible under the parent. It's not true of course but it shows how weird the current implementation is, if even Jira representatives are misled by it.
Right now the inline editing features are only in Team Managed projects. BUT!!! Guess what, we are bringing the same front end of Team Managed Projects for Boards and Backlogs into Company Managed Projects!
This means not only more modern look and feel but also a lot of improvements and efficiencies such as this one to be available across all project types.
We have just started rolling out early access to the new Boards and Backlogs in Company Managed Projects - would you want the ability to turn that on and give us your feedback?
Here's the relevant community article and the link to sign up :)
Atlassian Team members are employees working across the company in a wide variety of roles.
May 14, 2023 edited
No worries! would there be anyone here who would like to schedule a 30 minute call to go over how youre going with these changes, and/or other ease-of-use pains you have with Jira Software you want to tell a product manager about :)
Very cool new features, thanks! But still no threaded comments? Even a button that inserts a comment as a quote would help keeping conversations cleaner. I don't know any other modern collaboration apps that don't have a possibility for replying to comments.
61 comments