Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

How do you make an issue read only after it is in a closed status?

Edited

This is a big audit problem for us. After an issue has been closed, you can still make edits to the issue.

3 answers

2 accepted

2 votes
Answer accepted
Dirk Ronsmans
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 16, 2020

Hi @annag ,

You can do this by adding a property on the workflow. On the Status that you wish to block the editing go to properties and add:

 jira.issue.editable = false

issue editable.PNG

Thank you!!!

1 vote
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 16, 2020

You can block them with workflow properties.

See https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html

but in this case, find the status that is "closed" (one or many), edit the workflow and add jira.issue.editable = false to those status (you might want to do the same for comments and other permissions)

Thank you! Yes, looks like this removed the Edit capability. Would I use a behaviour to take away the edit capability for comments?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 16, 2020

On that page, there's mention of how you can do the same for comments.

Dirk Ronsmans
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 16, 2020

@annag ,

That would be through the jira.permission.* property.

Without duplicating all the information here there is an elaborate article about this on:

https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status

The one you are looking for I believe would be:

jira.permission.comment.denied = denied

Thank you so much! I will take a look at that doc.

Dirk Ronsmans
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 16, 2020

It's a bit older information (2011) but the information should mostly be accurate.

If they no longer work let me know and I'll do some testing myself :)

Harry Bob
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.
Jun 17, 2020

Will this work on next-gen projects within JSD?

Looking for a way to do this in a Behaviour...

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events