When a work item's status is changed, jira should compel the developer to add comments.

[P Vinod Kumar]

When a work item's status is changed, jira should compel the developer to add latest comments for that workitem. If the comments are not provided it will have the same status. If the latest comments are added, the workitem will move from current status to New status. Please help to set the rule

[Trudy Claspill]

Hello @P Vinod Kumar 

Welcome to the Atlassian community.

You cannot use the Automation Rule feature to meet this requirement. Automation Rules are triggered by the completion of an action. The rule could not be triggered until the transition is completed, so it cannot prevent the transition from completing.

As @pawarsachin84 suggested, this can be done by modifying the Workflow, if you are using a Company Managed project.

(Get the project Type information from the View All Projects page under the Projects menu.)

You would add a Transition screen to the Transition in the Workflow where you want to require the comments entry. Adding a Transition screen is only possible in workflows that are used in Company Managed projects. That feature is not available for Team Managed projects.

https://support.atlassian.com/jira-cloud-administration/docs/map-a-screen-to-a-workflow-transition/

In addition to the Transition screen, you would add a Validator for Field Required to the same transition to require an entry in the Comment field. If there is no entry the Validator does not pass and the user is not allowed to complete the status transition.

https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-validators-for-company-managed-projects/

[Trudy Claspill]

Hello @P Vinod Kumar 

Thank you for the update, Sachin and Trudy. I have implemented a validation process that checks for empty comments whenever a work item changes status. If the comment field is empty, it prompts the developer to "Update Comments." However, despite updating the workflow, the system is not recognizing the comments and continues to display the same message.

Can you show us the Validator you created?

Did you add a Transition Screen to that same transition? Can you show us a screen image of the transition? Here's an example of what I'm looking for:

If you did add a transition screen, can you show us an image of that screen being shown when you make the transition?

Lastly, can you show us the workflow diagram pointing out the transition you have changed? This is an example of what I'm looking for:

[P Vinod Kumar]

[P Vinod Kumar]

I have attached the screenshot of the workflow. Requirement completion is the Transition. When the requirement gets completed and if the developer moves it to done status, if the comments are empty it should prompt the developer to update the latest information. After providing the comments it should allow the workitem to move to done state.

[Trudy Claspill]

Hello @P Vinod Kumar 

Thank you for that image, but it does not match the example I showed. In my example I am using the original/old Workflow Editor. It appears that you are using the new workflow editor.

Specifically I would like to see the Validator information. In the new Workflow Editor you may see this in a panel on the right under the heading Rules.

Can you also provide us with images of the screens you see when you are executing the transition within an issue? I would like to see that you are getting prompted to add a comment, and that even when the Comment is filled in you get a message and are blocked from proceeding to complete the transition.

[P Vinod Kumar]

[P Vinod Kumar]

[Trudy Claspill]

Thank you for those images. That is helpful.

In my answer from July 17 I asked you to tell us the Type of project this concerns. Can you provide that information now? 

The solution described works only for a Company Managed project and requires the use of a Transition Screen. If you are working with a Team Managed projects this solution will not work for you.

[P Vinod Kumar]

Yes mine is company managed Project

[P Vinod Kumar]

[Trudy Claspill]

Thank you.

1. Are you wanting the user to be required to enter a new Comment as they execute the transition?

OR

2. Are you wanting to require that at least one Comment has been entered on the item at any time prior to execution of the transition?

The solution I described aligns with #1, but you did not implement it completely yet. For solution 1 you would need to also create a screen that can be shown during the transition so that the user can enter a comment during the transition, allowing the validator to check if a comment has been entered during the transition.

When the transition is attempted a pop up screen similar to this would appear, and the transition would not be allowed to complete until the user entered something in the Comment field.

[P Vinod Kumar]

I wanted to extend my heartfelt thanks for your excellent solution regarding the workflow validation in Jira. Your guidance was instrumental in resolving my issue. I truly appreciate the time and effort you put into helping me.

Could you also let me know if I have to do "2. Require that at least one Comment has been entered on the item at any time prior to execution of the transition? "What I have to do differently.

[Trudy Claspill]

There is not a native Validator available that check for Comments pre-existing in the issue, excluding any comment that is entered during the transition.

Options would be:

1. In the transition use a Condition instead, specifically the Value Field Condition to check that Comment is != to <empty Value field> when compared as String. That will prevent the transition from even being available if there are no pre-existing Comments on the issue.

2. Create a custom field to keep a count of Comments added to an issue, and populate that field using an Automation Rule. Then use a Validator to check that custom field value is greater than 0. You might also need a rule to change the custom field value when Comments are deleted. This rule might run frequently so you would need to consider the impact to the Automation Rule Execution limits for your subscription.

3. Look for a third party app that extends Workflow capabilities and supports more options for executing that specific validation. 

[pawarsachin84]

Hello @P Vinod Kumar , 

I can recommend (using Workflow Screens and making the Comments field required on the transition screen) is almost always the best solution. It's user-friendly, immediate, and uses native Jira capabilities. 

[P Vinod Kumar]

Thank you for the update, Sachin and Trudy. I have implemented a validation process that checks for empty comments whenever a work item changes status. If the comment field is empty, it prompts the developer to "Update Comments." However, despite updating the workflow, the system is not recognizing the comments and continues to display the same message.