Dependencies and automation across fields

[Paolo Pastorino]

I added a field named "Architectural review needed" (Y/N), and I would like to have the field "Architectural review done" automatically ticked (yes) if the corresponding architectural review is not needed.

Any idea about how to link the two and create those dependencies/automations?

Thanks

[Chris Timms]

Hello @Paolo Pastorino

Would a single multi-select field with multiple options not serve your purpose better?

If you do want to keep the two fields separate, then you can automate this process very simply in Jira Automations, which are available in JPD project settings.

Your rule would look something like:

Trigger when issue field is updated

• Architectural review needed - changed to "no"

Edit Issue

• Architectural review done - "Yes"

[habib rahman]

I have a similar question 🙋‍♂️ as well. Can we have the option for a user to pick an option for example, if someone picks yes, another field will open up they carry on if they pick no, they do not need to fill in some parts of the JSM forms. 

Thanks in advance 

[Haddon Fisher]

This is (right now) not possible without an add-on like ProForma.

FYI, ProForma was purchased by Atlassian and pieces of it are making it's way into core (forms is a good example) so it may be coming soon(ish) down the road. It is unfortunately no longer available in the Cloud marketplace though.

[Haddon Fisher]

I need to amend my answer a tiny bit - the other way I can think of to do this is the ScriptRunner feature "Behaviors". The just released it on Cloud, and while as of now I believe this is restricted to a handful of system fields, the Server version of this is much more robust and I have to believe they will expand it on Cloud at some point.

Hopefully.

Maybe.

Possibly.

At some point before the heat-death of the universe.