Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-10077

Refactor permissions code to get rid of "jira.issue.subtasks-creatable"

    XMLWordPrintable

Details

    • 1
    • 1

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      While implementing jira.permission.* attributes in 3.6, it became apparent that the permissions code would need some refactoring before we could implement 'jira.permission.subtasks.create'. So a hacky alternative, "jira.issue.subtasks-creatable" was left in the code. Unfortunately this cannot be edited through the workflow editor, being an internal (jira.*) property. We should finish the refactoring and implement the proper jira.permission.subtasks.create attribute.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-26208 Subtasks can be created even when create permission is removed via Workflow state Properties

          • Medium - Medium priority issues
          • Gathering Impact

          Suggestion - JRACLOUD-5476 Restrict Create Subtask to certain user groups only

          • Gathering Interest
          is related to

          Suggestion - JRACLOUD-8521 Add permission type Create Sub-Tasks ( better: Create Sub-Issues )

          • Closed

          Suggestion - JRASERVER-10077 Refactor permissions code to get rid of "jira.issue.subtasks-creatable"

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              7ee5c68a815f Jeff Turner
              Votes:
              38 Vote for this issue
              Watchers:
              23 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: