Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Releasing is not removing issues from board because of security level

Avira Operations GmbH & Co. KG June 19, 2020

Hi together, 

I'm currently facing the issue that we have three security levels applied. 

Default -> visible to all

NLC -> visible for Assignee, Project Role - Administrators, Project Role - Service Desk Team, Reporter

Participants Only -> visible for Assignee, Reporter, custom field (Participants), tec_user (used for automation) 

We are working with a Kanban board, doing a release every two weeks. We have no Release Manager as we are doing this in some kind of rotary style that everyone of the team does the release once.
Issues containing the default or nlc security level can be released without having any issues, but the issues having "participants only" can not be released. I already verified that the release can not be done because of the security level, because after changing it there's no problem with releasing anymore. 

As those information are confidential, I now need to find a solution on how this issue could be solved. I was already trying to use some kind of automation, but also here I'm stuck. 

Ahh, almost forgot we are running a Jira Software 8.8.1 and Service Desk 4.8.1

Best regards

1 answer

0 votes
John Funk
Community Champion
June 19, 2020

Hi @Avira Operations GmbH & Co. KG ,

It sounds like t me that you just need to designate a particular person to Release those issues each period. Give them the authority to see the issues and do the release.

The other option that MIGHT work is to create an Automation Rule that runs as the add-on and does the release. Then add the atlassian-addons group to the Security Level. 

Suggest an answer

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

Atlassian Community Events