Hello - Any thoughts on adding predecessor/successor functionality within Advanced Roadmaps? Predecessor/successor functionality should shift dates as stories are scheduled into sprints. I envision using this functionality at higher levels in the plan.
I found this work around however being able to add predecessors/successors is key to doing long term planning. I'd be fine with using blocks and blocked by if the dates moved. I'm managing a project with 10 different technical teams and need to understand when one teams dates shift how it impacts the entire project.
Successors / Predecessors in Advanced Roadmap (atlassian.com)
Hello,
Go to the project settings -> screens and add the time tracking field to the screens.
You can see the Estimated time, Remaining Time and Logged time in the Time Tracking panel. It is added by default. It is available after you provide a value for the Original Estimate field or you log work.
Hi Alexey,
Thank you for your answer. Here's what I did.
I went to the "Project settings", but there is not "screens" option there. I did see the "screens" before so went looking for it. Found it in the "Jira settings" under the "Issues" I found a "Screens" option
So "Jira settings | Issues | Screens"
For all screens I added the the "time tracking" and "log work" .
From here I can expect the see the work-logging-fields on the items in my project?
Thank you again!
Bob
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It means that you created a next-gen project. Next-gen projects do not have the time tracking feature. You would need to create a classic project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That does explain a lot.... then to help my search... do you have some handles on how to "convert"/"move" a next-gen project to a classic project?
Thanx!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You should create a new classic project and use bulk move to move issues from the next-gen project to the classic project.
You can find more info about bulk edit here:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanx! figured it out yesterday as well. The moving process went smooth... enough... only lost links between epics an stories. Not sure if I missed a "checkbox" or that this is a "designed".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You did not miss anything. It works like this.
If my answer helped you, kindly accept my answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.