Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-1857

JIRA subtask shows stale status information when it is closed from JIRA

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Linked JIRA subtask shows a resolve button after successfully resolving it. http://img.skitch.com/20090723-gsssdq4awmb7u8n4sakrw81t76.png

            [CRUC-1857] JIRA subtask shows stale status information when it is closed from JIRA

            Marek Parfianowicz added a comment -
            Atlassian Update – 5 October 2018

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Regards
            Marek Parfianowicz
            Fisheye/Crucible TL

            Marek Parfianowicz added a comment - Atlassian Update – 5 October 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Regards Marek Parfianowicz Fisheye/Crucible TL

            Adam Myatt added a comment -

            Seems to be present in 2.7.11 I created a Jira Issue through a code review, went to Jira and resolved it. Then waited an hour went back to code review in FECRU and the issue still shows as open in the code review.

            Adam Myatt added a comment - Seems to be present in 2.7.11 I created a Jira Issue through a code review, went to Jira and resolved it. Then waited an hour went back to code review in FECRU and the issue still shows as open in the code review.

            TimP added a comment -

            After some discussion with the other developers, we've decided to push this issue out to version 2.2. We're intending to revisit Crucible-JIRA integration with a view to pushing updates in both directions, rather than the rather expensive polling method used currently.

            TimP added a comment - After some discussion with the other developers, we've decided to push this issue out to version 2.2. We're intending to revisit Crucible-JIRA integration with a view to pushing updates in both directions, rather than the rather expensive polling method used currently.

            Robert Sfeir added a comment -

            I think that if you refresh the file in Crucible, by either clicking away from the file and back, or reloading the browser window and clicking on the file name, you really should refresh your cache at that point. I don't think that happens. I am not expecting AJAX like notification updates between Jira and Crucible, however I don't know what the original poster intended or was expecting.

            Robert Sfeir added a comment - I think that if you refresh the file in Crucible, by either clicking away from the file and back, or reloading the browser window and clicking on the file name, you really should refresh your cache at that point. I don't think that happens. I am not expecting AJAX like notification updates between Jira and Crucible, however I don't know what the original poster intended or was expecting.

            TimP added a comment -

            The linked issue is cached for a maximum of five minutes. So if you resolve the issue from JIRA and then view the comment in Crucible you may see out of date information.

            Crucible is smart enough to read through when you resolve it via the resolve link on the issue though. I think caching in this case is a sensible option, else you could end up with a large number of requests to JIRA every page refresh.

            This may be a candidate for a Won't Fix?

            TimP added a comment - The linked issue is cached for a maximum of five minutes. So if you resolve the issue from JIRA and then view the comment in Crucible you may see out of date information. Crucible is smart enough to read through when you resolve it via the resolve link on the issue though. I think caching in this case is a sensible option, else you could end up with a large number of requests to JIRA every page refresh. This may be a candidate for a Won't Fix ?

              Unassigned Unassigned
              sruiz Seb Ruiz (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:

                  Estimated:
                  Original Estimate - 4h Original Estimate - 4h
                  4h
                  Remaining:
                  Time Spent - 0.5h Remaining Estimate - 4h
                  4h
                  Logged:
                  Time Spent - 0.5h Remaining Estimate - 4h
                  0.5h