Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11156

Technical Task (sub-task) creation from Issue Type Story inherit Parent's Component

XMLWordPrintable

      Summary

      Contrary to JRA-14810 Sub-tasks quick creation for should inherit the components of the parent issue for new sub-tasks, creating a Technical Task from a Story issue type inherit the parent's component value

      Steps to Reproduce

      1. Install JIRA Agile
      2. Create JIRA Agile project
      3. Add a Component(s) to the project
      4. Create issue with issue type Story and populate the component field
      5. Create a Technical Task (sub-task) from the issue
      6. Leave the Component field blank

      Expected Results

      Component value from parent is not inherited

      Actual Results

      Component value from parent is inherited

      Notes

      Technical Sub-task came with JIRA Agile, not with the JIRA default sub-task

            [JSWSERVER-11156] Technical Task (sub-task) creation from Issue Type Story inherit Parent's Component

            Hoang Dong (Inactive) added a comment -

            Many thanks for raising this bug. Since there has not been any customer activity on this issue in over a year, we’re closing it as Timed out.
            If you feel that the bug is still relevant to your needs, please leave a comment and we'll reassess it.

            Kind regards,
            Dong Hoang
            JIRA Software

            Hoang Dong (Inactive) added a comment - Many thanks for raising this bug. Since there has not been any customer activity on this issue in over a year, we’re closing it as Timed out. If you feel that the bug is still relevant to your needs, please leave a comment and we'll reassess it. Kind regards, Dong Hoang JIRA Software

            Matthias Kuchem added a comment -

            If you "fix" this issue, please give another option to inherit the component(s), like prefilling the field on creation screen.

            Matthias Kuchem added a comment - If you "fix" this issue, please give another option to inherit the component(s), like prefilling the field on creation screen.

            Gaël NEUEZ added a comment -

            Hi,
            this ticket has been raised following a Support ticket of mine (JSP-203476).
            What I can tell is that it seems to only affect the Agile subtask: we have other subtasks types with different workflows, and they do not reproduce the parent component problem.
            In our configuration, we are running JIRA6.2.7 with JIRA Agile 6.4.2.
            Hope this helps.
            Regards
            Gael

            Gaël NEUEZ added a comment - Hi, this ticket has been raised following a Support ticket of mine ( JSP-203476 ). What I can tell is that it seems to only affect the Agile subtask: we have other subtasks types with different workflows, and they do not reproduce the parent component problem. In our configuration, we are running JIRA6.2.7 with JIRA Agile 6.4.2. Hope this helps. Regards Gael

            Oswaldo Hernandez (Inactive) added a comment -

            I thought so too mtokar :/

            dwatania@atlassian.com, can you confirm that the behaviour is only limited to this sub-task type, or has the behaviour changed for all JIRA subtasks. Can you also provide JIRA and JIRA Agile versions mate?

            Thanks in advance.

            Cheers,
            Os.

            Oswaldo Hernandez (Inactive) added a comment - I thought so too mtokar :/ dwatania@atlassian.com , can you confirm that the behaviour is only limited to this sub-task type, or has the behaviour changed for all JIRA subtasks. Can you also provide JIRA and JIRA Agile versions mate? Thanks in advance. Cheers, Os.

            Michael Tokar added a comment -

            ohernandez@atlassian.com I can't see why JIRA Agile would be overriding this behaviour. The sub task type "Technical task" is created by JIRA Agile but no special logic should be attached to it. If the value for the Component field is not being inherited, that sounds like an issue with that field/JIRA Core.

            At any rate, these claims should be investigated by Support and further documented before being determined an actual bug.

            Michael Tokar added a comment - ohernandez@atlassian.com I can't see why JIRA Agile would be overriding this behaviour. The sub task type "Technical task" is created by JIRA Agile but no special logic should be attached to it. If the value for the Component field is not being inherited, that sounds like an issue with that field/JIRA Core. At any rate, these claims should be investigated by Support and further documented before being determined an actual bug.

            Oswaldo Hernandez (Inactive) added a comment -

            Hi mtokar / mjopson,

            Is this behaviour intentional?

            Thanks.

            Cheers,
            Os.

            Oswaldo Hernandez (Inactive) added a comment - Hi mtokar / mjopson , Is this behaviour intentional? Thanks. Cheers, Os.

              Unassigned Unassigned
              dwatania@atlassian.com Daniel Watania (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: