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!
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}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It just doesn't populate the field with the now date
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It did throw this error in the audit log, but I have Start Date in the issue template.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looks like we do have 2 custom fields called Start Date. One is locked due to a plugin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you talking about the other Start Date field? I can move that to trash.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I deleted the unlocked Start Date and retested. It worked as it should. Thanks for the help!
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.