You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
There are a few reasons why you can’t edit the status of an issue in a plan.
The first is because Advanced Roadmaps plans are a “sandbox” environment we’d need to ensure that it was clear that the change wasn’t having an immediate effect (and if it did, then changing the status would be different from all other changes). At the moment we aren't clear what the correct approach should be ... i.e. the updated status change is pending until committed, or the change is immediate.
Secondly, depending upon your issue workflow it might be a requirement to provide additional data to the issue at the time of changing the workflow. Arguably we could support simple transitions where screens aren't required to be completed on transition though as this would be a simpler problem to solve and might address the majority of cases.
So although we recognise that value in being able to change workflow status from within a plan, there are significant challenges to making sure that this is a clear and intuitive experience.
But the final reason is that there is a very simple workaround to the problem (i.e. to go directly to the issue and change the status from the issue screen). There are a huge number of feature requests we have and when it comes to prioritising them we take factors like this into consideration. The fact that there is a workaround reduces the priority against features where there is no workaround.
I hope that explains why this capability isn’t available at the moment - that isn't to say we don't think this would be an incredibly valuable feature. It's definitely something I'd like to see added but we only have a limited number of developers available and are unable to address all the feature requests as quickly as we'd like.
At the moment this feature isn't on our immediate roadmap so you shouldn't expect to see it added in the near future. I appreciate that this isn't the answer you're hoping for, but I just wanted to be honest and set expectations realistically,
Hi and thanks for updating!
Completely appreciate the rationale as you have explained it but I cannot see how enabling this change is different from say, the ability to reassign a story to a colleague or to create a new story under an epic. All of these changes are 'pending' until published to the Jira project and so, any advanced roadmaps user will know this as a default. As you mentioned, it is a "Sandbox" environment so this type of change shouldn't differ from the others.
Even in the example you provide of further info being required prior to transitioning in a workflow, this is imposed by the project and therefore, as you mention, roadmaps can simply support transitions where this is not the case (Simple transitions with no blockers).
Quite rightly, there is a workaround but I must say, it isn't a great user experience nor is it a deal-breaker. My logic is; for small change - big impact items like this, it's a no brainer...
I'm definitely not disagreeing with you @Steven Stroffolino ... and I probably agree that it would make sense to make the change pending until committed, I also agree that we could use the same approach as we do for required fields on commit... it's not that it's impossible to, just that it's necessarily a quick fix.
But in terms of priority let's compare with features such as Next-Gen project support, exporting plans as an image, support for editing description, additional custom field type support, individual capacity management, etc (please note I've just listed some common requests off the top of my head, these aren't all features we're currently working on!)... all customers have different perspectives on what the most important feature is and not all of them have simple workarounds.
However, I do completely agree this would be an incredibly useful feature and one that I would use on a daily basis.
It is extremely painful to have to go back to my kanban board and search through dozens if not hundreds of cards to change status. An easy fix that would add a lot of value, would be to add click and change functionality in advanced roadmaps. All changes need to be reviewed before committing, so seems like an obvious feature add.
Dear Atlassian Team
How can you be so ignorant and not implement a simple functionality for more than 3 years now? I saw in JIRA dozens completely senseless and unneeded features and this one in really useful and important especially for PMs who work with roadmaps on the massive scale with hundred tasks. Switching in such a situation every time to the details of the task to change its status is unergonomic and time-consuming. It is really the waste of time. Please do something about it at last !!!!
Just to make sure, it's possible to update the assignee, and many, if not all of the fields' values (for an epic or issue) in the Advanced Roadmap, but the only field that cannot be updated is the status field?
We would really, really, really want to be able to update the status field from the Advanced Roadmap view. It would be terribly useful!
Thanks a lot!
We are currently releasing this feature in Advanced Roadmaps Cloud edition. You can read more about it on this announcement page: https://community.atlassian.com/t5/Advanced-planning-articles/Update-Issue-status-directly-in-Advanced-Roadmaps/ba-p/2534687#M675
Senior Frontend Engineer at Atlassian
We had the same issue, very inconvenient. I had to create a custom field that is a pull down that matched our status. I then setup automation so when that value is changed, it has an if else that transitions the issue to the correct status. Not elegant but works