block the change of a field

Іван Андрєєв March 23, 2023

is it possible to block the change of a field if another field is not filled?
We want that if the "Description" field is empty, we cannot put an assigner.

3 answers

3 accepted

1 vote
Answer accepted
Kelly Arrey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 24, 2023

Hi @Іван Андрєєв 

One approach you could try that doesn't involve automation is an Assign transition:

  • Make sure your Screen Scheme includes a separate Edit screen which does not include the Assignee field - 
  • Add one or more Assign transitions to your workflow
    • you can make them transitions to the current status e.g., from In Progress to In Progress,
    • or you can make them transitions to other statuses in the workflow
  • The important things are that:
    • You have a transition screen which should include the Description field and the Assignee field
    • You add a Field Required Validator to the transition to ensure that - you should add a meaningful message to tell the user that Description must be filled in to complete the transition

Of course, a user can satisfy this validator by typing "N/A", so this kind of enforcement is no substitute for a team that understands why it's important to include a useful description that includes the relevant information that the assignee will need in order to get the work done.

Іван Андрєєв March 28, 2023

@Kelly Arrey  Hi

it's an interesting idea, but I don't fully understand how to implement the dependency.

Kelly Arrey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 24, 2023

Hi @Іван Андрєєв, which parts are unclear? Are you working in a company-managed project or a team-managed project. Do you have Jira admin permissions or does someone else do your Jira administration?

0 votes
Answer accepted
Іван Андрєєв March 23, 2023

@Magdalena Zhisheva  Hi 

automation is not suitable for my management because you have to refresh the page to see the changes and the specialist may just think that he has appointed, but no. Here it is necessary to somehow forbid him from this action immediately, so that he has no choice. Block action.

0 votes
Answer accepted
Magdalena Zhisheva
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 23, 2023

Hi @Іван Андрєєв ,

I am thinking of two possible scenarios here:

1. Put a validator in the Workflow, i.e. the Description field will be required

2. Build an automation like this:

Screenshot 2023-03-23 at 16.44.46.png

Іван Андрєєв March 23, 2023

Hi @Magdalena Zhisheva 

automation is not suitable for my management because you have to refresh the page to see the changes and the specialist may just think that he has appointed, but no. Here it is necessary to somehow forbid him from this action immediately, so that he has no choice. Block action.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events