Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-270

JIRA change history shows garbage values for GH Rank field even when Rank field is unchanged, and doesn't update change history when rank does change

      This is really 3 bugs
      1. Our JIRA change history is littered with what looks like changes to the Rank field when no change was made. It happens for nearly every operation on an issue. this happens even when there is no change to Rank. This is confusing and just clutter. See below for an example.
      2. The value displayed currently in the JIRA change log for rank is meaningless - e.g. there is no Rank 219000000
      3. When I do drag and drop rank an item, there is no change to the change history in JIRA for rank but the rank value does change !

      Thanks for listening and helping.

      -------------------
      Change by Joel Feldman - 11/Feb/08 12:36 PM
      Fix Version/s Sprint 20-Red [ 10020 ]
      Rank 2190000000

      Change by Joel Feldman - 11/Feb/08 01:22 PM
      Fix Version/s Sprint 20-Red [ 10020 ]
      Rank 20000000

      Change by Chris Brookins - 19/Feb/08 07:28 PM
      Summary 78BL8Q ScheduleWizard: Clicking OK in Holidays form doesn't save the new business hours for the user 78BL8Q ScheduleWizard: Clicking OK in Holidays form doesn't save the new business hours for the user
      Rank 645000000

            [JSWSERVER-270] JIRA change history shows garbage values for GH Rank field even when Rank field is unchanged, and doesn't update change history when rank does change

            You guys rock!

            Chris Brookins added a comment - You guys rock!

            JC added a comment -

            I did some extra work on the bug GHS-269 for you Chris !
            I actually manage to trick JIRA to not make a change log on Issue updates.

            Still Issue screens are cool

            Cheers,

            JC added a comment - I did some extra work on the bug GHS-269 for you Chris ! I actually manage to trick JIRA to not make a change log on Issue updates. Still Issue screens are cool Cheers,

            JC added a comment -

            Hehe Chris, I am sure you are trying to promote your request GHS-266

            For your question 1.
            The ranking field is a field that GreenHopper changes in the back even if the Issue remains untouched.
            You have to consider it like a system field. You have no control on it, it will just tell you the position of your Issue.
            When you update an issue, JIRA submits all the fields. If a field has a different value then the old one it will be changed and logged.
            Since the ranking value may have changed the rank value since the last update of the issue, well most likely you will have a log.

            The answer to your question 2 will surely answer your concern:.
            And here it is:
            You can withdraw a field from the edit view if you create your own Screen Scheme with your custom screens.
            When you create a screen you decide what fields to see
            When you create a screen scheme you decide which screens to associate to which Issue operations (Edit, View, Create)
            You can then associate a screen scheme per issue type

            We use it a lot to customize our story view - task view and so on

            Here are some usefull links:
            http://www.atlassian.com/software/jira/docs/v3.12.2/fieldscreens.html
            http://www.atlassian.com/software/jira/docs/v3.12.2/fieldscreenschemes.html
            http://www.atlassian.com/software/jira/docs/v3.12.2/issuetype_screenschemes.html

            JC added a comment - Hehe Chris, I am sure you are trying to promote your request GHS-266 For your question 1. The ranking field is a field that GreenHopper changes in the back even if the Issue remains untouched. You have to consider it like a system field. You have no control on it, it will just tell you the position of your Issue. When you update an issue, JIRA submits all the fields. If a field has a different value then the old one it will be changed and logged. Since the ranking value may have changed the rank value since the last update of the issue, well most likely you will have a log. The answer to your question 2 will surely answer your concern:. And here it is: You can withdraw a field from the edit view if you create your own Screen Scheme with your custom screens. When you create a screen you decide what fields to see When you create a screen scheme you decide which screens to associate to which Issue operations (Edit, View, Create) You can then associate a screen scheme per issue type We use it a lot to customize our story view - task view and so on Here are some usefull links: http://www.atlassian.com/software/jira/docs/v3.12.2/fieldscreens.html http://www.atlassian.com/software/jira/docs/v3.12.2/fieldscreenschemes.html http://www.atlassian.com/software/jira/docs/v3.12.2/issuetype_screenschemes.html

            JC wrote >> But when you edit the issue, JIRA will commit all the values displayed in your edit screen (editable or not) so since it did change when ranking was done, JIRA will log it as a change history.

            OK, but if that is the case, I have 2 issues.
            1. Why doesn't JIRA log every other value displayed in our edit screen in our change history? No other custom or built-in JIRA field generates changes to the history if I don't edit those fields. Doesn't this seem like something GH should prevent?

            2. As you say, I can prevent this behavior by not displaying this custom field in the screens. But when I hide the Rank field from my Default and Workflow screens I no longer see the Rank value when I just am viewing an issue. I agree there is no reason for me to see that field when I am editing an issue, but I don't know how to tell Jira that I want to see the value of the Rank field when viewing an issue but hide rank when editing an issue. Can you help me do that? It is critical that I see the Rank field when I inspect an issue - and I agree I don't need to see it when editing an issue...at least I don't need to do so until you implement GHS-266

            Chris Brookins added a comment - JC wrote >> But when you edit the issue, JIRA will commit all the values displayed in your edit screen (editable or not) so since it did change when ranking was done, JIRA will log it as a change history. OK, but if that is the case, I have 2 issues. 1. Why doesn't JIRA log every other value displayed in our edit screen in our change history? No other custom or built-in JIRA field generates changes to the history if I don't edit those fields. Doesn't this seem like something GH should prevent? 2. As you say, I can prevent this behavior by not displaying this custom field in the screens. But when I hide the Rank field from my Default and Workflow screens I no longer see the Rank value when I just am viewing an issue. I agree there is no reason for me to see that field when I am editing an issue, but I don't know how to tell Jira that I want to see the value of the Rank field when viewing an issue but hide rank when editing an issue. Can you help me do that? It is critical that I see the Rank field when I inspect an issue - and I agree I don't need to see it when editing an issue...at least I don't need to do so until you implement GHS-266

            JC added a comment - - edited

            Hi Chris.

            The Change log is due to adding the field to your edit view of the issues.
            When you rank the value changes and like you said we dont log changes for it.
            But when you edit the issue, JIRA will commit all the values displayed in your edit screen (editable or not) so since it did change when ranking was done, JIRA will log it as a change history.

            The Rank value that you see is not an absolute value of the rank but a relative value based an an algorithm that we used to prevent updating all the issues when only 1 issue was moved. (Performance and waiting reasons) - Bringing an issue from rank 1000 to 1 will have triggered 1000 updates ....

            Cheers,

            JC added a comment - - edited Hi Chris. The Change log is due to adding the field to your edit view of the issues. When you rank the value changes and like you said we dont log changes for it. But when you edit the issue, JIRA will commit all the values displayed in your edit screen (editable or not) so since it did change when ranking was done, JIRA will log it as a change history. The Rank value that you see is not an absolute value of the rank but a relative value based an an algorithm that we used to prevent updating all the issues when only 1 issue was moved. (Performance and waiting reasons) - Bringing an issue from rank 1000 to 1 will have triggered 1000 updates .... Cheers,

              jchuet JC
              6d80a6d00f16 Chris Brookins
              Affected customers:
              2 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: