I suggest Structure Plugin should ...

Disallow closing a parent until all child issues are closed.

68 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    BenBen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    7 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Matti TaivaljärviMatti Taivaljärvi commented  ·   ·  Flag as inappropriate

        Hello,

        Please consider in this plan also the vice versa request that when all children are closed the parent should be closed automatically also. I guess this should be configurable somehow per structure as other structures might see it so that parent still needs to be specifically closed.

      • Igor SeredaAdminIgor Sereda (Admin, ALM Works) commented  ·   ·  Flag as inappropriate

        Roy - thanks for your comment!

        As for the dates, we cannot promise any release dates for features, sorry. So far this feature does not make it into the next release, so it is not likely that it will be ready earlier than September.

        But your votes are duly noted and we'll definitely give more attention to this item at our next planning session.

        Thanks!
        Igor

      • Roy MoshkovitzRoy Moshkovitz commented  ·   ·  Flag as inappropriate

        We need the option of prohibiting the dragging /attaching open issues under a closed parent.

        It is very important for our organization to use the methodology because we are integrating with external issue database, when can we have it done?

      • Igor SeredaAdminIgor Sereda (Admin, ALM Works) commented  ·   ·  Flag as inappropriate

        There's also a question with permissions - the user may have permissions to resolve only some of the issues.

        From your perspective, if the user has permissions to close/complete an issue, does that mean that he should also have permissions to close/complete any of that issue's children and parent issues?

      • Igor SeredaAdminIgor Sereda (Admin, ALM Works) commented  ·   ·  Flag as inappropriate

        Ben, thanks for the idea!

        We can do the following: the plugin shall provide a workflow validation function, which JIRA admin can add as a pre-condition to Resolve workflow action. So if you have open sub-issues, the Resolve action won't be available.

        To force closure of all children is a bit more tricky, considering that the notion of Close Issue is configurable and that an issue can have subissues from different projects and with different workflows.

        Apart from that, we'll need to address what happens when the user moves an open issue under a closed issue, or if they create a new issue under a closed issue. The options are: a) prohibit that; b) reopen closed issue (also subject to configuration per workflow); c) close the moved-in child issue (does not make much sense for new issues).

      • BenBen commented  ·   ·  Flag as inappropriate

        If I've got child issues/tasks on a parent issue, it shouldn't be completed until those child issues are closed. Alternatively, closure could force closure of all child issues.

      Feedback and Knowledge Base