I need the issue status to be changed based on he due date filed.
for example: I need a certain ticket (not a jql list of issues) to be reopened on 17.32 of 31st of December (or in any other date that I manually set).
I went through community and tried to google it and I managed to find this thread:
It was suggested to use this addon: https://marketplace.atlassian.com/apps/1211836/automation-for-jira-server-lite?hosting=server&tab=overview
The only issue is that it's for server jira while we're using cloud jira...
The only function I need is to schedule the issue to be reopened - could you please suggest a free cloud addon allowing to reopen the issue at a manually set time?
Additionally I need to set the date and the time, for example 17.32, 18.48, 23.59, etc.
Hello @Ilya Konovalov ,
For cloud it was by default enabled.
Can you please go to the below path on your project ->
1. Go to Project
2. Project settings
from the above, you can create automation rules within the project.
Kagithala Babu Anvesh
I simulated one automation in my environment and provided it below:
In this automation when the Due Date field was changed:
And the due date is after the start date:
Here you can choose the fields:
- Date time
And when the result of the condition meets the rule, it will be transferred to TO DO:
This is how it works: The issue is closed (implemented), and the due date is later than the start date, so when I changed the value this issue went back to TO DO.
It's just an example, but you can customize it as you like. 🤝
But it should be noted that with this automation applied to a global rule, they will consume their execution limits, this applies to
Multiproject and global consumption.
Project-specific does not consume, it is unlimited.
Below, I provide the explanation and related documentation.
Automation for Jira Cloud
In Jira Cloud, automation functionality is included out-of-the-box. However, there are limits to how many times rules can be executed per month, depending on which plan you’re on:
Free plan: There is a limit of 100 executions for all global and multi-project rules.
Standard plan: There is a limit of 500 executions for all global and multi-project rules.
Premium plan: There is a limit of 1,000 executions per user per month, pooled across all users and products. For example, if you have 200 users in your Jira Cloud Premium license, then you’ll have a limit of 200,000 global/multi-project rule executions per month.
Automation for Jira Cloud
Below I provide some knowledge databases related:
Have an awesome day!
I'd implement it like this:
"Re-open date" < now() and status != "To Do"
I haven't tried it, but even if it is imperfect, at least it should give you the idea.
Thank you Aron!
That's what I needed! :)
Unfortunately, the reply from João wasn't what I needed as it would trigger the issue when the due day filed is changed while I need it it to be checked when the condition due date < actual date is True.
But I appreciate the help from all of you! Thank you very much and have a happy new year
Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events