Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-11209

Version name and Description fields are editable but they don’t save changes on Agile plan mode

XMLWordPrintable

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

      Symptoms

      This affects JIRA versions 6.3.4 and higher, regardless of the JIRA Agile version installed.

      When viewing Agile boards in plan mode, by expanding the Versions session it is possible to click on the Description field to make it turn into a text box. After entering some value and hitting <enter> it looks like the description has been updated, however, when we refresh the page it gets back to the old value (or empty if there was no description before).




      Work around

      Please edit version data through the Versions page in Project Administration.

        1. after_changes.png
          after_changes.png
          73 kB
        2. before_changes.png
          before_changes.png
          72 kB
        3. description_entered.png
          description_entered.png
          74 kB
        4. mouseover_description.png
          mouseover_description.png
          75 kB

            [JSWCLOUD-11209] Version name and Description fields are editable but they don’t save changes on Agile plan mode

            Ansgar Schmidt added a comment -

            Have the same problem.

            Ansgar Schmidt added a comment - Have the same problem.

            Mattias Nord added a comment - - edited

            This is definitely a weird issue and also affects JIRA On Demand, but here's a little fast workaround.

            Always keep the issues "planned" for a future release in a version called "Next release", since this acts as a filter, then when you are ready to package a new release, just create the new release version f.ex. "1.1.0", then click the "Next release" to list all issues, then drag and drop all issues from "Next version" to your new "1.1.0" version.

            Mattias Nord added a comment - - edited This is definitely a weird issue and also affects JIRA On Demand, but here's a little fast workaround. Always keep the issues "planned" for a future release in a version called "Next release", since this acts as a filter, then when you are ready to package a new release, just create the new release version f.ex. "1.1.0", then click the "Next release" to list all issues, then drag and drop all issues from "Next version" to your new "1.1.0" version.

            Kevin Smith added a comment -

            Big problem for us, +1

            Kevin Smith added a comment - Big problem for us, +1

            Tadas Labudis added a comment -

            When is this going to be resolved?

            Tadas Labudis added a comment - When is this going to be resolved?

              Unassigned Unassigned
              jraupp Jose Raupp (Inactive)
              Affected customers:
              11 This affects my team
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: