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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Can you please tell how can I automatically set start date when ticket moved from To Do ---> In Progress column in classic Jira kanaban board.
Like we have in in Next Gen
Manage rules -> Add rules -> Update an issue field ->For issues moving to (In progress) -> Update this field (start date)
Hi @GZ
To Do
In Progress
Start date
{{now.plusDays(0)}}
Thank
I followed your mentioned steps, but when I move the issue start date does not appear on ticket.
Any idea?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Take a look in the audit log of you automation rule. Perhaps there are some errors.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How do you add the condition to check that the Start Date is EMPTY before updating it? Start Date does not appear in the list of fields to check. Thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does anyone have a reply to this question as I am trying to do the same thing. Only set the start date if it has not already been set.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For some reason it is not accepting the way that the smart value is disposed...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @GZ
To make the automation rule to work as intended, the automation user executing the rule (Automation app user) should be allowed to edit the issue. That being said, check the following steps:
Let us know if you have any questions.
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.
I worked it out using automation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Jack would you be able to add a screenshot of your rule configuration? Im a newbie.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @GZ
Check if you have option in post functions of this transition in the workflow.
Later after the changes, you can set the same in kanban board settings.
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.