Different access restrictions across issue types within the same Jira space?

[Nat Grauman]

I would like to have a single Jira space that allows our business partners to request work via “Action” issue types and then when our product dev team is ready to commit to the work, we convert those issue types to Capabilities, but we don’t want the business partners to be able to convert to capabilities, create capabilities, or edit the issues after they become capabilities. Is this possible?  

[Dev]

Hi Nat,

Yes, this is possible, but it requires some configuration.

You can allow your business partners to create Action issues, and when your product team is ready, they can transition or convert them to Capability issues.

After the issue becomes a Capability, you can use Issue Security Levels or workflow conditions/properties to restrict who can view or edit it. This allows only your product team to modify the issue, while business partners can no longer edit it.

By combining project permissions, workflow restrictions, and issue security, you can achieve the behavior you're looking for.