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

Development field is not retrieving up to date build state

      Issue Summary

      The Development field in the Advance issue search is not populating the build state correctly even though the build state is seen when we open the full issue view.

      Steps to Reproduce

      1. Create a build for an issue from GitHub.
      2. Once the build state is completed we can see the updated  Development panel within Jira with the build state.
      3. But when we check the same within the Advance search the build state is missing and is shown blank.

      Expected Results

      The development field should ideally show the build state in both in full issue view as well in the Advanced issues search once it is updated in Jira.

      Actual Results

      Build State is not populated and is shown blank.

      Workaround

      We have to open the issue in full issue mode and then going back to advanced search will show the build state.

        1. 1.jpg
          1.jpg
          30 kB
        2. 2.jpg
          2.jpg
          11 kB
        3. 3.jpg
          3.jpg
          22 kB

            [JSWCLOUD-23831] Development field is not retrieving up to date build state

            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 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.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            In your "culture of being honest and open", I'd suggest you just clearly state that you won't fix things. What's the point in prompting people to let you know that they "feel like this bug is still impacting" them?

            You have not fixed it. So, yes, of course it does.

            Daniel Franz - JXL 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 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. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team In your "culture of being honest and open", I'd suggest you just clearly state that you won't fix things. What's the point in prompting people to let you know that they "feel like this bug is still impacting" them? You have not fixed it. So, yes, of course it does.

            Atlassian Update - October 16, 2024

            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 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.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - October 16, 2024 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 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. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

            Just to clarify: The odd thing is that the build data is shown correctly in the Advanced Issue Search, but only after the issue has been viewed in the full issue view ("Bento").

            Therefore, to reproduce, please go as follows:

            1. Create a build for an issue from GitHub.
            2. View the issue in the Advanced Issue Search, and add the “Development” column. Note that the Development column is empty for the issue. This is the bug.
            3. Open the issue, and see the build data in the Development panel.
            4. Reload the issue in Advanced Issue Search. Note that the Development column now also shows the build data.

            Hannes Obweger - JXL for Jira added a comment - - edited Just to clarify: The odd thing is that the build data is shown correctly in the Advanced Issue Search , but only after the issue has been viewed in the full issue view ("Bento"). Therefore, to reproduce, please go as follows: Create a build for an issue from GitHub. View the issue in the Advanced Issue Search, and add the “Development” column. Note that the Development column is empty for the issue. This is the bug. Open the issue, and see the build data in the Development panel. Reload the issue in Advanced Issue Search. Note that the Development column now also shows the build data.

              Unassigned Unassigned
              c04d6e5d39c6 S Naveen Kumar (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: