Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Create operation validation not checked when an issue is moved

Mayuresh Sakharape
Contributor
March 17, 2023

Hi,

I have project A. It has 2 issue types Story and Bug. Issue type Story creation is restricted to role PO with workflow validation. User with role Developer has created Bug. Now he moved the issue form type Bug to Story. This move operations works. So here user with role Developer has created a Story whose creation is restricted to role PO. So JIRA is not checking the validation here.

Is it a bug or expected behavior? How can this be restricted without restricting the move permission.

Kind Regards,

Mayuresh

1 answer

1 vote
Oday Rafeh
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 17, 2023

Hi @Mayuresh Sakharape , I hope you doing fine 

 

This behaviour is expected in Jira because the move operation doesn't strictly follow the same validation rules as creating a new issue. When moving an issue, Jira checks the Move Issue permission rather than Create Issue permission.

To restrict the move operation based on user roles, you can use a workflow condition instead of validation. Here's how you can add a condition to the workflow transition for the move operation:

  • Go to your Jira instance and click on the gear icon (Settings) in the top-right corner.
  • Click on "Issues" in the left sidebar, then click on "Workflows" under the "Workflows" section.
    Find the workflow associated with the issue types (Story and Bug) and click on "Edit" to modify it.
  • Click on the "All" tab in the workflow designer to view all transitions.
  • Find the "Move Issue" transition (or the transition that allows moving issues between types) and click on it.
  • Click on the "Conditions" tab in the transition properties panel.
  • Click on the "Add condition" button and select the "User is in project role" condition.
  • Configure the condition to restrict the move operation to the "PO" role.
  • Publish the changes to the workflow.


Now, only users with the "PO" role will be able to move issues between the Bug and Story issue types. This way, you can ensure that only users with the appropriate role can change the issue type without restricting the Move Issue permission directly.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.20.11
TAGS
atlassian, atlassian government cloud, fedramp, webinar, register for webinar, atlassian cloud webinar, fedramp moderate offering, work faster with cloud

Unlocking the future with Atlassian Government Cloud ☁️

Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.

Register Now
AUG Leaders

Atlassian Community Events