Error "We couldn’t restrict your issue type. Refresh the page and try again." while trying to restrict Subtasks on a Team Managed project

Still need help?

The Atlassian Community is here for you.

Ask the community

For Atlassian eyes only

This article is Not Validated and cannot be shared with customers.

(warning) Delete this section above the line before publishing your KB




Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.


Summary

Unable to restrict subtask work type on Team managed project, error "We couldn’t restrict your issue type. Refresh the page and try again." is encountered

Environment

Jira Software Cloud 

Diagnosis

Try to use the restrict Subtasks in a Team Managed Software project for users having specific Project role it will throw an exception "We couldn’t restrict your issue type. Refresh the page and try again" 

Cause

This is a UI Bug i.e. the API which is being used to restrict work types is not applicable on Subtasks. Due to this, Jira will throw an exception. Ideally, the UI should not show us the lock option for Subtasks work types.

Solution

  • Generate HAR file and for "issuerestrictions" web request you will see below error message

  • Ideally the option to restrict Subtasks issue types should not appear on UI
  • Subtasks work are supposed to be created when you want to further breakdown the work in standard worktype in smaller units/work
  • Issue restriction should be applied for Standard issue types (Story, Bug, Task etc) and the same should be inherited by the linked child Subtasks
  • As a workaround you can edit the workflow of Subtasks and under Create transition use Rule validator "Validate that people have a specific permission" define the Permission. Users with that specifc permission can only create subtasks work type, however this wont refrain other users from viewing the subtasks work created.


  • Work level security is inherited from Parent work type, for example restriction is set for Task work type, now when a user without that role creates a Task, the Task is created, however, the user is unable to Browse the Task and thus wont be able to create the Subtasks under the restricted parent.


Last modified on Mar 31, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.