When creating an Issue, prevent logging to specific Project OR Project Category (HOW TO)

[Luke]

Hello, I am wondering if the following is possible using either automation (but I can't find a suitable solution) or e.g. with a post function / validator on the Create Issue workflow transition – something akin to the 'Parent Status Validator' option but for Project/Category instead:

---

When user goes to create a new Issue

If Project (OR, optionally Project Category) is X (or Y category)

Then user cannot create Issue (error message much like using other 

---

Essentially I am trying to stop users logging to one specific project. I know it's an odd use case and you'd think I could just close that project, but I do have my reasons! 

[Dexter de Vera · Accepted solution]

Hi @Luke ,

Base on my knowledge, there is no condition to validate the project. For me, some workaround, you may create a different permission scheme to the specific project and align group or role to control who can create (or any other permission) on that specific project. 

Hope it helps,

Thank you!

[Marc - Devoteam]

Hi @Luke 

Set different permission schemas and in the permission schemes, use groups and user for the permissions, not roles.

Project admins can grant a role to any user, but by not using roles but defining the permission on group and/or user level in a permission scheme, you are are to limit which users can see which projects.

[Luke]

Thank you!

[Tessa Tuteleers]

Hi @Luke , 

You can restrict "Create issues" permission for the projects you want to rectrict to certain user groups or roles. 

More info about permissions here. 

Please let me know if I misunderstood and your case is more complex thant this.

- Tessa