I want to add an approver whenever someone changes due date. This due date change should be done with a reason. Whenever anyone tries to change due date, he should add reason then this is sent to approver to accept/reject the changes. This should be managed without any workflow transition and to be purely field level validations.
Hi Neha - Welcome to the Atlassian Community!
This is a little more complicated but can be done.
You would need to create a new screen with either a custom field where the user has to populate something, or you could just use the Comments field.
Then add a self looping transition on the status - a transition that starts with the status and ends with the same status. Then add the screen you created to the transition along with a Validator to for Field Required for your custom field or the comments field, whichever one you decided.
Then create a new automation rule for when the field is edited to send an email to the Approver with information in the field.
The transition to the next status would have a condition so that only the Approver can execute it. So for the approval, the Approver just moves the issue to the next status.
Can you share the rule that you have so far?
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.
@John Funk the solution seems to be too complicated. Is there any other way around to achieve this? Primary motive is to track due date changes with reason.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can't have your cake and eat it, too. :-) If you don't want the fields shown on the screen, there is not another way I know if to do this. Complicated or not, if it works, why not do it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't find the condition to show fields through automation. Hence, asked you a way around.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can't force a user to add values to fields using Automation. That has to be done in the workflow as described above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can't do this natively; there is no approval process for fields being modified.
You could use Automation to notify specific user(s) via email if a due date is changed? They could then review the change, and reverse it if needed.
---
You might also be able to do something more complex with Automation - for example...
First rule...
Second rule...
...but this seems complex to me.
---
Aside from this, alternatives would be...
---
Let us know your thoughts :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your reply @Ste Wright I'm trying to automate to populate 2 new fields if due date value is changed. But I am not able to show those fields. I don't want these fields to be shown by default in the form. These fields to be visible only if due date is changed. Is there something I am missing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The fields don't need to be on a Screen to populate them.
But there's no Automation Rule which would "visualise" those fields based on a due date being changed.
If you want the Fields to be visible, they need to be on the Screen (regardless of the logic).
---
You might be able to do this using an App, such as Scriptrunner for Jira utilising behaviours?
Ste
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.