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

Creating an Issue in the Agile Board sets resolved date

XMLWordPrintable

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      • Create an Issue in the planning mode of a scrum board
      • The issue counts towards resolved issues in the project overview, because the resolved date is set

      Workaround:
      When you start to work on the issue the resolved date disappears.

            [JSWSERVER-11129] Creating an Issue in the Agile Board sets resolved date

            Carla Ann K. Rowland added a comment -

            @mtokar

            This is still happening in Data center 

            JIRA Software is 8.20.6

            Carla Ann K. Rowland added a comment - @mtokar This is still happening in Data center  JIRA Software is 8.20.6

            Carla Ann K. Rowland added a comment - - edited

            @mtokar

             

            This is still happening in Data center 

            JIRA Software is 8.20.6

             

             

             

            Carla Ann K. Rowland added a comment - - edited @mtokar   This is still happening in Data center  JIRA Software is 8.20.6      

            Michael Tokar added a comment - - edited

            Dear customers,

            To those who are still experiencing this bug even after upgrading JIRA Agile on their Server instance, we apologise for the inconvenience. It turns out the fix to this issue was not deployed in a new version of JIRA Agile, but in a new version of one of our JIRA bundled plugins, the Inline Issue Create Plugin.

            The version of the plugin which contains the fix, 0.3.1, was deployed to our Cloud customers some time ago. It was included in our JIRA Server release 6.3.11. Please upgrade to that version or higher to fix this issue.

            Regards,
            JIRA team

            Michael Tokar added a comment - - edited Dear customers, To those who are still experiencing this bug even after upgrading JIRA Agile on their Server instance, we apologise for the inconvenience. It turns out the fix to this issue was not deployed in a new version of JIRA Agile, but in a new version of one of our JIRA bundled plugins, the Inline Issue Create Plugin. The version of the plugin which contains the fix, 0.3.1 , was deployed to our Cloud customers some time ago. It was included in our JIRA Server release 6.3.11 . Please upgrade to that version or higher to fix this issue. Regards, JIRA team

            Nick Shaw added a comment -

            No; just updated to 6.6.51 and the issue is still happening as described.

            Nick Shaw added a comment - No; just updated to 6.6.51 and the issue is still happening as described.

            Bernd Junk added a comment -

            Does the update to 6.6.51 solve this problem on server instance?

            Bernd Junk added a comment - Does the update to 6.6.51 solve this problem on server instance?

            Nick Shaw added a comment -

            We're on JIRA Agile 6.6.41 (server instance), and we're still seeing this happen. Is it planned to be a future rollout to download instances?

            Nick Shaw added a comment - We're on JIRA Agile 6.6.41 (server instance), and we're still seeing this happen. Is it planned to be a future rollout to download instances?

            Michael Tokar added a comment -

            This issue has been resolved for our JIRA Cloud customers.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - This issue has been resolved for our JIRA Cloud customers. Regards, JIRA Agile Team

            Frank S. added a comment - - edited

            The display of a wrong status (strikethrough on the issue key) in plan-mode is confusing for users.
            Any progress on this issue?

            Frank S. added a comment - - edited The display of a wrong status (strikethrough on the issue key) in plan-mode is confusing for users. Any progress on this issue?

              Unassigned Unassigned
              64cfb42d4486 Thomas Fischer
              Affected customers:
              3 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: