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

XMLWordPrintable

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

      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

            cgottlieb@atlassian.com Caz (Inactive)
            0ed961e27eb4 Erwann (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: