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 block worklog changes and deletion on certain statuses

Hi, 

It is possible to block users from logging time spent on tickets in a specific status using the jira.permission.work.denied workflow property key.

But this leaves the possibility of deleting or modifying the worklogs.

I want to block the deletion and modification of worklogs with a specific status.
I tried using jira.permission.worklogdeleteall.denied and jira.permission.worklogeditall.denied but it doesn't seem to work

Do you have any suggestions?

regards, 

 

1 answer

1 vote
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 11, 2023

Hi @Melanie Liguet,

I have not tried going so far in restricting permissions personally using workflow properties to be honest, but you may be running into this issue that is mentioned in workflow properties documentation :

2023-11-11 12_19_26-Useful workflow properties for Jira Cloud _ Jira Service Management Cloud _ Atla.pngI am not sure where in your workflow you are trying to apply these restrictions. A common scenario is to do this in a closed status and then it is quite common to deny any more updates to the issue whatsoever, which you do with the jira.issue.editable = false property. 

Hope this helps! 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events