Hello,
I setup a workflow with automatic customfield update when peoples transition issues.
This customfield is a condition on transition to define differents ways to move in my workflow.
In jira plan (advanced Roadmap) we are able to select additional fields to show in plan.
....but the famous customfield is editable on plan whereas it's not on issue edit screen and consequently, workflow condition is not applicable because the field doesn't match with expected value
I don't find yet if I can disable edit on jira plan for some customfields.
For the moment, I use automation to trigger when the field has been changed, I get the previous value and overwrite the value added by user via jira plan.
Do you know if we have a solution to disable edit field value for some customfields?
Thank you in advance.
Cedric
Question- Not a answer..
Which automation rule did you use to get previous value? Thanks
Hi Sanwar
Here a example:
1. I create a automation rule to check if a field A has been updated
2. I compare original value vs the new one
3. If values are different I get the old value and reapply value
Finally, you have to use smartvalue "changelog ... from" in order to get original value
ex: {{changelog.customfield.fromString"
So it's an alternative solution to prevent that value is not changed.
Cedric
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.
Hello @Dan Rushing
To block issue edit is not possible so the alternative solution is to overwrite value entered from plan with the original value .
Here a example:
1. I create a automation rule to check if a field A has been updated
2. I compare original value vs the new one
3. If values are different I get the old value and reapply value
Finally, you have to use smartvalue "changelog ... from" in order to get original value
ex: {{changelog.customfield.fromString"
So it's an alternative solution to prevent that value is not changed.
Cedric
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @CEDRIC DEVAUX , interesting use case.
The condition only prevents the transition in the workflow, it doesn't say anything about the custom fields being editable or not.
Let me test this and get back to you.
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.