We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 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.

      A problem we currently have to workaround is the fact that we sometimes log high-level features that we then split into many smaller tasks, which we then link using a "subtask" link. I'm certain many companies do something similar.

      The problem is that since for JIRA links are meaning-less, effort estimated on the high-level task won't be kept up-to-date with the effort involved in subtasks, etc.

      In order to workaround this problem we have to specify quite a complex procedure for our developers.

      If instead JIRA detected (or defined) this "subtask" links between issues, it would know it needs to add/substrack effort accordingly, etc.. and it would save developers & managers the effort.

        1. rendition of feature enhancement.jpg
          rendition of feature enhancement.jpg
          110 kB
        2. screenshot-1.jpg
          screenshot-1.jpg
          461 kB
        3. subtasks.png
          subtasks.png
          21 kB

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 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.

                A problem we currently have to workaround is the fact that we sometimes log high-level features that we then split into many smaller tasks, which we then link using a "subtask" link. I'm certain many companies do something similar.

                The problem is that since for JIRA links are meaning-less, effort estimated on the high-level task won't be kept up-to-date with the effort involved in subtasks, etc.

                In order to workaround this problem we have to specify quite a complex procedure for our developers.

                If instead JIRA detected (or defined) this "subtask" links between issues, it would know it needs to add/substrack effort accordingly, etc.. and it would save developers & managers the effort.

                  1. rendition of feature enhancement.jpg
                    rendition of feature enhancement.jpg
                    110 kB
                  2. screenshot-1.jpg
                    screenshot-1.jpg
                    461 kB
                  3. subtasks.png
                    subtasks.png
                    21 kB

                        nick.menere Nick Menere [Atlassian] (Inactive)
                        ff68bb20b387 Paco Vidal
                        Votes:
                        209 Vote for this issue
                        Watchers:
                        104 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            nick.menere Nick Menere [Atlassian] (Inactive)
                            ff68bb20b387 Paco Vidal
                            Votes:
                            209 Vote for this issue
                            Watchers:
                            104 Start watching this issue

                              Created:
                              Updated:
                              Resolved: