Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-5869

Sub-Task should have independent security levels

XMLWordPrintable

    • 11
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      When creating a sub-task, it automatically inherits the security
      level of its parent. Using the workaround described in JRA-5442,
      it is possible to change the security level of the sub-task, e.g.
      to hide special tasks from your customers.

      However, it is not possible to set the ("hidden") security level
      upon creation of the sub-task. So, if you want to create a
      private sub-task, that is not accessible by your customers, you have
      to first create a sub-task that is automatically private, hence
      generating an automatic eMail notification of your customer. Then,
      you have to edit the sub-task to change the security level.

      Wouldn't it be more efficient to let the user choose the security level
      when creating the sub-task?
      Or could we have special security levels for different types of sub-tasks.
      E.g. create a sub-task "private sub-task" that automatically relates to
      a certain security level "private".

      (Just to explain: We are using Jira Enterprise 3.0.3 to track new
      features. It is used by us and our clients. When a new feature issue is
      created, we put several development/private sub-tasks under it, to
      split work for one feature or to assign private work that has to
      be done in order to build the new feature. But we do not want our
      customer to see, what is going on "behind the scenes".)

            [JRASERVER-5869] Sub-Task should have independent security levels

            Terrell added a comment -

            If your organization has the ScriptRunner plugin, you can easily work around this by adding a post-function on the create transition using Script Post-Function [ScriptRunner]. Select the option to "Set issue security level depending on provided condition". If the condition is always true, just type "true" in the condition box and then select the name of the security level.

            Terrell added a comment - If your organization has the ScriptRunner plugin, you can easily work around this by adding a post-function on the create transition using Script Post-Function [ScriptRunner] . Select the option to "Set issue security level depending on provided condition". If the condition is always true, just type "true" in the condition box and then select the name of the security level.
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3062069 ] New: JAC Suggestion Workflow 3 [ 3693402 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Chris Terry made changes -
            Link New: This issue is duplicated by JRASERVER-65857 [ JRASERVER-65857 ]

            rahul jaiswar added a comment -

            i tried with the above approach but it did not worked out for my case

             

            rahul jaiswar added a comment - i tried with the above approach but it did not worked out for my case  

            Amin added a comment -

            Thank You @irenemweu . It was awsome and worked,

            Amin added a comment - Thank You @ irenemweu . It was awsome and worked,
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2600210 ] New: JAC Suggestion Workflow [ 3062069 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2583394 ] New: Confluence Workflow - Public Facing v4 [ 2600210 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]

            Eric Kramer added a comment - - edited

            Super disappointing.  @Dave Meyer can you elaborate on why this won't be implemented? Seems like a huge gap in the security and usefulness of coordinated subtasks.  Thanks -EK

            Eric Kramer added a comment - - edited Super disappointing.  @Dave Meyer can you elaborate on why this won't be implemented? Seems like a huge gap in the security and usefulness of coordinated subtasks.  Thanks -EK
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2347073 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2583394 ]
            Maja (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-67744 [ JRACLOUD-67744 ]

              Unassigned Unassigned
              97476c182d14 Andreas Deimer
              Votes:
              187 Vote for this issue
              Watchers:
              124 Start watching this issue

                Created:
                Updated:
                Resolved: