Currently, a workflow is set to require three fields when a ticket is closed.
However, if a ticket is closed for reason "Duplicate" we do not want these fields to be required.
How can I set this up?
How do you require the fields? Through the Field Configuration Scheme or the workflow validators? If it's through the workflow, I'm assuming you use the Validator.
The 3 fields make this difficult. If it was only one, you could add a condition with the Value Field (assuming you have JSU), setting the Resolution = Duplicate, and having that be one condition. You could then add another condition for value field, setting it to be not empty, effectively requiring it. You would then set the Workflow to go with "Any of the following Conditions" instead of All, and remove the validator. Since there are 3 fields, this would require any of the 4 conditions, and would only make one required.
The easiest way I can see would be to add a separate transition to Closed. You can name it "Duplicate", and it would show up as a separate button next to Close. This Duplicate transition would not have the workflow validator that requires the fields. You could even add a validator that sets the resolution to duplicate.
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
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