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

Date timestamp of changes in state are not correctly captured - NULL

    XMLWordPrintable

Details

    • 4
    • Severity 3 - Minor
    • No

    Description

      Issue Summary

      When the state of a work item is changed the correte date timestamp is not being captured in all scenarios. If the user changes the state on JA and hit save, it got recorded, but if the same happens without the save (like being changed on Jira and synced to JA), the timestamp is not recorded even though the state changes.

      Steps to Reproduce

      1. Create a Feature on JA, let it sync with Jira
      2. Change the State on JA
      3. Check the tables (or EI) and notice that the timestamp was capture related to that state
      4. Now change the State on Jira and wait it to sync
      5. Check the same data and you will notice that the timestamp of the change was not captured on the correct fields

      Expected Results

      Regardless of how the state changes, the timestamp will be captured on the corresponding fields.

      Actual Results

      Depending on how the state is changed, the timestamp is not captured accordingly.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

       

      Fix Existing Data

      https://hello.atlassian.net/wiki/spaces/JALN/pages/1515568477/ALIGNSP-11354+-+State+Timestamp+Recording

      Attachments

        Issue Links

          Activity

            People

              pkreidenkov@atlassian.com Pavlo Kreidenkov
              a8cff3407f0b Diego Larangeira
              Votes:
              3 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync