Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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?

 

 

2 answers

2 accepted

1 vote
Answer accepted
Pramodh Community Leader Jan 26, 2021

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 Community Leader Jan 26, 2021

FYI,

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

Hi @Pramodh ,

Thanks for the detailed information.

Thanks.

Like Pramodh likes this

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

I implement this solution, thanks again.

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

Pramodh Community Leader Jan 27, 2021

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

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?

0 votes
Answer accepted

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,184 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you