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

cloned issues with sub-tasks do not display properly in GreenHopper

XMLWordPrintable

      When a user clones an issue that has sub-tasks (and includes the task in the cloning), the task does not show up with the correct issue in GreenHopper. The cloned task shows up under the original issue, not the cloned issue.

            [JSWSERVER-724] cloned issues with sub-tasks do not display properly in GreenHopper

            JC added a comment -

            Good new Atlassian fixed the Issue that was preventing GreenHopper to react properly to the "Clone Issue"
            See: http://jira.atlassian.com/browse/JRA-15949

            This should then be fixed for JIRA 3.13.2

            Cheers,

            JC added a comment - Good new Atlassian fixed the Issue that was preventing GreenHopper to react properly to the "Clone Issue" See: http://jira.atlassian.com/browse/JRA-15949 This should then be fixed for JIRA 3.13.2 Cheers,

            JC added a comment -

            I have been talking to the someone one the JIRA team.
            There is nothing we can do to support this currently with the way JIRA is handling the issue cloning.

            The JIRA team will change the way they actually clone issues to let other plugins know about that event.
            We will then be able to trigger the proper action regarding the ranking field them.

            The change should be released in JIRA 4.0

            We will need to be patient

            Cheers,

            JC added a comment - I have been talking to the someone one the JIRA team. There is nothing we can do to support this currently with the way JIRA is handling the issue cloning. The JIRA team will change the way they actually clone issues to let other plugins know about that event. We will then be able to trigger the proper action regarding the ranking field them. The change should be released in JIRA 4.0 We will need to be patient Cheers,

            Jennifer Durkee added a comment -

            This happens when sort by is set to "ranking". Re-ranking the cloned issue fixes the problem.

            Jennifer Durkee added a comment - This happens when sort by is set to "ranking". Re-ranking the cloned issue fixes the problem.

              Unassigned Unassigned
              43319afc6b1f Jennifer Durkee
              Affected customers:
              1 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: