This issue is related with the fix of issue JRA-14032
      Steps:
      1. Create a new issue and create some sub task for that issue.
      2. Suppose we have sub task blocking condition activated for the project in the workflow.
      3. Once all sub task are closed, user closes the parent issue.
      4. Now User can't create new sub task for closed parent issue.
      5. Try reopening the subtask without reopening the parent issue.

      Result:
      1. User can reopen the subtask for a closed parent issue.

      Expected:
      1. User should n't be allowed to reopen the issue till parent issue is not reopened/open.

            [JRASERVER-17192] User can reopen a sub task for a closed parent issue

            Rodolfo Romero added a comment - - edited

            Hi Edwin,

            Thanks for your reply. In that case, I believe this ticket should be reopen as there is no plugin available to do this kind of validations which opens the door to inconsistencies within Jira.

            Rodolfo Romero added a comment - - edited Hi Edwin, Thanks for your reply. In that case, I believe this ticket should be reopen as there is no plugin available to do this kind of validations which opens the door to inconsistencies within Jira.

            edwin added a comment -

            Hi Rodolfo,

            Unfortunately, this condition isn't available in the core JIRA product.

            At the time of writing, Anton was referring to a transition that was available as one of our sample plugins with our plugin system: http://confluence.atlassian.com/display/JIRA/How+to+create+Custom+Workflow+Elements+for+JIRA+3. However, since the launch of JIRA 4, we have a new plugin system. Unfortunately, there are no equivalent samples at this stage for the new plugin system.

            You may, however, look for plugins in our plugin exchange which accomplishes this: plugins.atlassian.com.

            Regards,
            Edwin
            JIRA Product Management

            edwin added a comment - Hi Rodolfo, Unfortunately, this condition isn't available in the core JIRA product. At the time of writing, Anton was referring to a transition that was available as one of our sample plugins with our plugin system: http://confluence.atlassian.com/display/JIRA/How+to+create+Custom+Workflow+Elements+for+JIRA+3 . However, since the launch of JIRA 4, we have a new plugin system. Unfortunately, there are no equivalent samples at this stage for the new plugin system. You may, however, look for plugins in our plugin exchange which accomplishes this: plugins.atlassian.com. Regards, Edwin JIRA Product Management

            Anton, how do you do that? I can only find options to customize the workflow on the parent side based on the status of the sub-tasks.

            Rodolfo Romero added a comment - Anton, how do you do that? I can only find options to customize the workflow on the parent side based on the status of the sub-tasks.

            AntonA added a comment -

            I think we should leave this as is. If this behaviour is not desirable, users can customise their workflow and protect the Reopen transition such that if the parent is closed it is not possible to resolve/close (or whatever) the subtasks.

            AntonA added a comment - I think we should leave this as is. If this behaviour is not desirable, users can customise their workflow and protect the Reopen transition such that if the parent is closed it is not possible to resolve/close (or whatever) the subtasks.

              Unassigned Unassigned
              vbharara Veenu Bharara (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: