Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,881
Community Members
 
Community Events
176
Community Groups

Is there functionality to help me lock order of tasks and update timelines based on previous changes

I am using the Advanced JIRA roadmap as a tool to help project manage cross team projects. It is a replacement of Gantt for us and works great because instead of a passive spreadsheet, we can connect each task to the teams' boards which makes planned work more visible and planning easier to coordinate.

What am I currently missing / spending a lot of time manually resolving:

  • I want to be able to separate tasks by Level 1 and Level 2 processes. Right now, I'm using Epics for Level 1 and Stories for Level 2 but because I can't nest Tasks within a Story, I'm using the order of the tickets to dictate the flow of the works. This is pretty flawed because as soon as somebody filters by date or task name, the whole order goes out of the window and has to manually be corrected. I have tried using Sub tasks nested within Tasks which works for things that are covered in the same sprint but breaks down as soon as some of the Sub tasks are covered in one sprint and the others in the next. Is there a way to nest Tasks into Stories, and Stories into Epics?
  • Even when nested, within every Level 2 process there are 10-20 steps (Tasks) and the order of these is important. Is there a way to hard code the order of the tasks, and have this as a "sort by" option? 
  • Very often, delays in one activity have a waterfall effect on everything else. Every time a date changes upstream, I have to manually adjust all the tasks' dates that happen thereafter. Is there a way to hard code the duration of each task and by changing one tasks' start dates, this to automatically update all the upcoming tasks as well?

It would be great to hear if any of these features exist or workarounds that can help me get to what I need. Looking forward to hearing from you!

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events