Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-2785

PI details panel- Create single sprint- Warning when duplicate wipes all entered data

    • 1
    • Severity 3 - Minor
    • X-Men - VH6
    • No
    • None

      Issue Summary

      The warning behavior in inconsistent in some spaces in Jira Align. In some places, the information remains for users to act on the warning, but will be cleared out in other places.

      There is 2 location where a single sprint can be created:

      1. Create button>Sprint
      2. from an anchor inside PI> Sync sprint tab> Single add

      The Sprint creation inside a PI (2. ) wipes the pre-filled information when triggering duplicate warning.

      This does not occur in 1. as if the sprint is a duplicate, the warning will display but will retain the information already filled.

      Steps to Reproduce

      1. Create button>Sprint 

      1. Select the create button, top right
      2. select create sprint
      3. enter a sprint information
      4. when added, repeat same operation to force a duplicate
      5. notice the warning message but the information remains

      2. inside PI> Sync sprint tab> Single add 

      1. Go to a PI
      2. Go to Sync sprint
      3. Select 'Single Add'
      4. enter a sprint information
      5. when added, repeat same operation to force a duplicate
      6. notice the information is cleared went he duplicate warning occurs

      Expected Results

      in both scenario the manually filled information should remain if a warning appears, so the user can correct his entry

      Actual Results

      User get the warning but all informations are cleared

      Workaround

      For the time being, using solution 1. instead of 2. may assist users in the sprint creation

            [JIRAALIGN-2785] PI details panel- Create single sprint- Warning when duplicate wipes all entered data

            Closed in 10.93, 
            Now fields' data doesn't disappear after showing warning message on creating sprint from PI Sync sprint tab
            https://jira.atlassian.com/secure/AddComment!default.jspa?id=1713271

            Caz (Inactive) added a comment - Closed in 10.93,  Now fields' data doesn't disappear after showing warning message on creating sprint from PI Sync sprint tab https://jira.atlassian.com/secure/AddComment!default.jspa?id=1713271

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug report but admit that not each one will be resolved with high priority. To continue the culture of being honest and open, we are changing the priority of this bug from High to Medium priority to focus on some other critical bugs that may be impacting you and our other customers.

            As we continue to resolve other bugs, we do look at requests made by our users, and if you feel like this bug is preventing your team from critical workflow, please let us know.

            Thank you again for providing valuable feedback to our team!

            Sunny Xu

            Sunny Xu (Inactive) added a comment - Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug report but admit that not each one will be resolved with high priority. To continue the culture of being honest and open, we are changing the priority of this bug from High to Medium priority to focus on some other critical bugs that may be impacting you and our other customers. As we continue to resolve other bugs, we do look at requests made by our users, and if you feel like this bug is preventing your team from critical workflow, please let us know. Thank you again for providing valuable feedback to our team! Sunny Xu

              cgottlieb@atlassian.com Caz (Inactive)
              0ed961e27eb4 Erwann (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: