Workflow properties - Restrict Attachment Delete to selected groups only

Muhammad Tahir January 14, 2025

Scenario:

A user has created a ticket.

L1 Agent picks up the ticket and update ticket with their finding and attach some documents. At this step agent can delete their own attachments (for this configured project permission to delete own attachments).  L2 agent can also delete all attachments at this level.

L1 agent transition the case to next level (e.g. Initial Working to Review Working), at this step case is assigned to L2 agent, now L2 agent should be able to add/ remove all attachments.

 

Configured workflow properties in following manner but not able to achieve the desired results.

 

Workflow status: Initial Working

Property Key: jira.permission.attachdeleteall.group.include 

Property Value: L1 group ID, L2 group ID

 

 

 

Workflow status: Review Working

Property Key: jira.permission.attachdeleteall.group.include 

Property Value: L2 group ID

 

 

 

 

1 answer

0 votes
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.
January 14, 2025

Hi @Muhammad Tahir and welcome to the Community!

Have you tried without the .include to specify your property. That is not supposed to be there:

jira.permission.attachdeleteall.group

For more details and examples, see also this support article

Hope this helps!

Muhammad Tahir January 15, 2025

I will try, but I have users in two groups L1 and L2. If we put them same group then we have to manually manage this new group in addition to existing ones.

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.
January 15, 2025

If you can't add both groups into one property, add the property twice (for each group). 

Muhammad Tahir January 15, 2025

it does not allow the same proper to be added twice, already tried this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events