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
Next: Root
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
Hi everyone, I am a real newbie to Jira and have been trying to solve this for last 24hours without finding an solution. So under the issues there are few subtasks that have set due dates and I would want Jira Automation to automatically update the issues due date based on the latest subtask due date. So automation would compare sub task due dates and would choose the latest due date and set it to issue duedate.
How can I do this? I have tried tens of combinations but have not succeeded to automatically update the issue duedate (that currently is always empty for all issues as I am only following subtask due dates)
Can someone help me? Like said, I started using Jira 3 days ago so an not familiar with most of the functions it has
The rule that works in my demo is:
If you need any screen from any step please let me know
I used if else statement because without else (checking if Due Date of parent is empty) statement automation rule does not worked when parennt issue does not have Due date field already set.
Best regards,
Piotr
Thanks Piotr, That setup went through and is now enabled, but however nothing changes on the project? I mean if I modify the sub-task dates, the issue date still remain empty no matter what I do? Am I missing something that would need to be enabled or set to make the automation work? Even the stock automations like "when all subtasks are done -> move parent to done does not take effect when I try.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, I took a look at the automation logs and from those it seems that the automation should be working, but it will still not change the due date of the issue? It just remain blank always
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just a few thoughts @Taneli Ylinen
1. Are the Due Date fields the same type of field in parent & child?
2. I'm not sure if it's possible to block the JA user, but if it is, are there special permission or security scheme restrictions on parent issue type?
3. Have you tried adding a logging statement to your JA, to see what value is being picked up from the child?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am running ionto the same issues as @Taneli Ylinen.
The rule has been made.... the rule seems to execute according to the rule executions overview in the issue, but the value of the related issue doesn't actually change.
I created a rule for blocked issues, so when an issue can not start before another issue is completed.
If the first issue has a new Due date, I want to copy that new due date to the start date of the blocked issue.
Attached are 2 screenshots. The first is of the rule, the second is of the first issue, where you can see that rules were executed.
It would be great to get some pointers
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.
Hi,
Please provide some more info/screenshots that will help us troubleshoot your problem:
Best regards,
Piotr
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is no Project role atlassian-addons-project-access in my project.
How do I add it?
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.