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

sprint isStarted smart value only ever returns false

      Issue Summary

      When using the sprint.isStarted or the issue.Sprint.isStarted smart values, only false is ever returned for a valid sprint. No value is returned for "none" as the sprint.

      Steps to Reproduce

      1. Create an automation in a Jira Software project that triggers on change of the sprint for the issue.
      2. set an action to send an email to yourself with the body containing the sprint.isStarted value (for debugging)
      3. apply an advanced compare operation to check if the sprint.isStarted value is ever equal to "true" and some action after that such as a comment to the issue to see if the condition passed.
      4. Save the automation and activate it.
      5. create a sprint, add an issue to that sprint.
      6. start the sprint, add another issue to the sprint.

      Expected Results

      At least one of the above issues returns "true" for the isStarted value and the automation is able to perform the correct action.

      Actual Results

      The automation only ever returns false, so the automation cannot run as expected.

      Workaround

      There is currently no known workaround for this issue.

            [JSWCLOUD-20717] sprint isStarted smart value only ever returns false

            Dylan added a comment -

            Hi all,

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

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.

            To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            Dylan added a comment - Hi all, Thank you for raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            Looks like AUT-2040 was shipped Wednesday and is working now, thanks folks!

            Drew Kerrigan added a comment - Looks like AUT-2040 was shipped Wednesday and is working now, thanks folks!

            Does seem to be an issue. We're fixing this as part of https://codebarrel.atlassian.net/browse/AUT-2040

            Mark Chaimungkalanont added a comment - Does seem to be an issue. We're fixing this as part of https://codebarrel.atlassian.net/browse/AUT-2040

              Unassigned Unassigned
              jlong@atlassian.com Jared Long
              Affected customers:
              2 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: