Can modifications to a bug be stopped once the final (Closed) status is reached?

[Holloway Winfred]

Is it possible to remove the capability for a user to update a bug's fields once the bug's final (closed) status is reached and a Resolution has been assigned? 

And if it is possible, would that keep the bug from being reopened?

[Pramodh · Accepted solution]

Hi @Holloway Winfred 

You can achieve this by using workflow properties.

Please follow the instructions below to get the requirement done :-)

Have the separate workflow for Bug Issue Type

In the last Status i,e closed you can have jira.issue.editable property set to false, the recommended way is to set the editable permission to a role/group (either Jira administrator or project administrator) using property  jira.permission.edit.group or jira.permission.edit.role

For Example

jira.permission.edit.group=jira-administrators

Thanks,
Pramodh

[Pramodh]

FYI,

If you have not edited the bug workflow, usually the workflow for the bug issue type is separate

[Kagithala Babu Anvesh]

Hi @Pramodh ,

Thanks for the detailed information.

Thanks.

[Holloway Winfred]

Yes, thank you for the additional details Pramodh.  I do have a separate Bug workflow,

I implement this solution, thanks again.

[Holloway Winfred]

One last question Pramodh, do you foresee an issue of resetting the "jira.issue.editable property to 'true' in a "Re-Open" transition?

[Pramodh]

That's a good practice, although you may want to limit the transition to certain roles or groups in here.

[Holloway Winfred]

Pramodh, I'm not sure where to implement the "jira.issue.editable=false" property update. 

Would that be set up by selecting the "View Properties" field associated with the applicable Transition on the Workflow Text (edit) page, which goes to a "Add New Property" page? 

Then by 'adding a new Property'; and placing  "jira.issue.editable" in the Property Key field, and "True" or "False" in the "Property Value" field?

[Kagithala Babu Anvesh · Accepted solution]

Hi @Holloway Winfred ,

By using default Jira Template we can't make it possible.

There may be possibilities with Adaptive Script Runner I think.

Please check with their documentation.

Thanks