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,462,039
Community Members
 
Community Events
176
Community Groups

Dynamically make an issue start once a predecessor is complete?

If we say an issues is blocked by another issue (or is dependent upon another issue) - can we set the start date of the second activity = the end date of the predecessor?

1 answer

0 votes

Hi @karen.loomis  -- Welcome to the Atlassian Community!

You seem to be asking two different questions with your post title and the question contents:

  1. can we dynamically start an issue once its predecessor has completed?
  2. using issue block links, can we set the start date of an issue based upon the end date (due date?) of the predecessor?

You could do both of these with automation for Jira rules... However for (1) starting an issue automatically when another finishes seems to me "pushing work" onto a team/person rather than letting them know: "this item can be started when you are available".

And for (2), you may want to consider the roadmap feature to see this visually rather than setting the dates with a rule.


Best regards,
Bill

Hi @Bill Sheboy,

could you expand a bit more on which automation could be used? Especially for (1)? I didn't find a trigger that targets a predecessor issue.

Best regards and thanks in advance!

Hendrick

Hi @lhz -- Welcome to the Atlassian Community!

You are correct that there is no built-in trigger...Instead consider using a Issue Transitioned trigger for the first issue, and then find the predecessor based upon how they are dependent.

For example, when using issue links for dependencies you could use JQL to find the issue and then take action on it within a branch.

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events