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,359,747
Community Members
 
Community Events
168
Community Groups

How do you automate the editing of the start and due date field on an issue when changing status?

We're trying to use advanced roadmaps more and have the feature toggled on that dynamically changes the epic done date based on when the child issues in the epic are slated to be worked in a sprint.

The problem is that we have a couple kanban teams as well, and we can't dynamically track the epic due date unless the child issues have dates in them. I wanted to create an automation rule that automatically assigns a start date to an issue when it's transitioned from To Do to In Progress and a due date when it's transitioned form In QA to Done using the smart value of {{now}} to add today's date, but that doesn't seem to be working. 

Does anyone have experience with doing something like this? Any help is appreciated. Thank you!

1 answer

1 accepted

1 vote
Answer accepted
John Funk Community Leader Aug 10, 2022

Hi Jordan,

What is not working with your rule? Can you share the rule here? 

You bet! I made it pretty simple, so it's likely I'm doing it wrong, but here's what I have:

 

When: Issue Transitioned

From: To Do

To: In Progress

THEN

Edit issue fields: Start Date

With: {{now}}

Like Joao Santos likes this
John Funk Community Leader Aug 10, 2022

And do you get an error in the audit log? Or it doesn't fire? Or it doesn't populate the field with the now date? 

It just doesn't populate the field with the now date

John Funk Community Leader Aug 10, 2022

Hmm, that's strange. Can you share an actual screenshot of the entire rule? And the audit log section where it runs? 

It did throw this error in the audit log, but I have Start Date in the issue template. Screen Shot 2022-08-10 at 11.28.44 AM.png

John Funk Community Leader Aug 10, 2022

So that's an issue if you have two fields named the same thing. The system field is Start date with lowercase d. Did you add a new field called Start Date with uppercase? 

If so, for testing purposes, edit the custom field and add a period at the end and save it. It should look like Start Date.

Then give it another test. 

Looks like we do have 2 custom fields called Start Date. One is locked due to a plugin. Screen Shot 2022-08-10 at 11.40.07 AM.png

John Funk Community Leader Aug 10, 2022

Yep, that's your problem. Jira doesn't know which one to deal with. Can you change the plugin one? Or even get rid of it since there is already one by that name? 

It doesn't let me delete it or alter it. It says its locked by Jira and I'm not allowed to alter its configuration. 

John Funk Community Leader Aug 10, 2022

What about the plugin date?

Are you talking about the other Start Date field? I can move that to trash. 

John Funk Community Leader Aug 10, 2022

Do it!  :-)  But you need to move data out of it first if there is something in there and not the system Start date field. 

I'm not sure I follow what you mean by moving data out of it. It's not associated to any screens, so would I be safe to trash it? 

I deleted the unlocked Start Date and retested. It worked as it should. Thanks for the help! 

Like John Funk likes this
John Funk Community Leader Aug 10, 2022

Great! Glad you got that worked out. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

4,955 views 18 31
Read article

Atlassian Community Events