Configuring workflow properties to restrict editing for issues

[Felix]

Hi there,

I am trying to use Jira Product discovery to source ideas from various teams within my organisation - however there are some fields i would like to lock down for editing to prevent fields being updated.

https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

I've had a look at workflow properties to determine that this can be locked down to edit permissions at specific statuses - I have the key based on the recommended documentation jira.permission.edit.projectrole but the example suggests that i need to provide a ProjectRoleID instead of the name of the project role e.g. Administrator or Creator - just wondering how i can find out what the ProjectRoleID for my role is? 

[Jeny Stoeva · Accepted solution]

Hi @Felix Liu , 

1. Open Settings (from the menu in the top-right corner, next to your Profile settings) > System > Project roles
2. Select a role, e.g. Administrator and click "Edit" on the right. The role will be opened for editing and you can of course cancel but at that point the role ID will be loaded in the URL and you can take it from there. 

This is how in general you can look up the IDs of different objects in Jira. 

[Felix]

Thanks! the IDs seemed to have worked - i ended up getting the jira cloud API to work and did a "Get project roles for project" so now it looks like i can configure jira.permission.edit.projectrole with the relevant ProjectroleID 

Thanks for your  help!

[Jeny Stoeva]

@Felix Liu You are welcome :) I was doing some AI automation on top of Jira and needed the ids of the different issue types. It was not straightforward to figure out from where to get them.

[Nick Haller]

Hi @Felix Liu ,

I believe some/most workflow properties are deprecated or unsupported - including the use case you shared above :(

We also understand 1) the documentation should reflect this, and 2) if these features are unsupported then they should not be offered within a JPD project's workflow.

Unfortunately this second part has been a bit more difficult to update since all JPD project's are team-managed and built on this foundation - meaning it would require an entire update on the project-type.

[Felix]

Hi Nick,

The JPD workflow and status properties seem to work - i've been able to lock down the edit permissions to admin users only using the ID and jira.permission.edit.projectrole 

Some of the documentation could be updated to give more examples on how we get some of the IDs to configure in the properties :) 

Thanks, 

[Nick Haller]

Hi @Felix Liu ,

That is good to know! Did you use the suggestion @Jeny Stoeva provided above, or go through the workflow properties of the JPD Workflow tab?

Could you possibly provide a screenshot of your settings? I've personally been unable to configure this after lots of testing so I'm very curious.

[Felix]

Hi Nick,

Yep i went through project settings --> workflow --> on the specific status i wanted to lock down on i added the key and put in the value of the projectroleID for the admin group i wanted to configure,.

Tested it out on a couple of users who were admins and a few that weren't - seems to be working (users who arent admin get an error saying that that the fields cannot be set which is pretty much what i wanted to achieve - stopping users from changing the ticket/item once it reaches a certain stage. 

[Nick Haller]

Hi @Felix Liu ,

Thank you for sharing! Very helpful. Last question from my end - where did you find the projectrole ID value? Is this a user's ID, a group's ID, and/or an actual project role ID?

I see in the workflow properties documentation, specifically under a similar example, it uses "2" as the value which I'm unsure of what the means or how to find it:

"Only allow a user who has the projectRoleId of 2 to comment on an issue."

^ I don't think I much of an idea of what that means or where to find a similar value to "2" 😅 Maybe through the API it's possible to find this??