Uploaded image for project: 'SR for Jira - Development'
  1. SR for Jira - Development
  2. SRJIRA-1046

disable jira's dirty form checking for fields that have been set through behaviour setValue

    Details

    • Type: New Feature
    • Status: Done
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.4.38
    • Component/s: Behaviours
    • Labels:
    • Sprint:
      Sprint 40, Sprint 41, Sprint 42, Sprint 43
    • Critical Points:
      0.7

      Description

      Either the value has been set on load, in which case it's not significant, or it has been set through modifying other fields, in which case their "dirty" property will kick in.

      So it's probably OK to set the saved initial value to the same as the "set" value./

      Proposed Solution

      We considered a number of different solutions for this issue.

      Our guiding principle is that we want to allow the administrator to specify the default value for a field, and not keep the original one just because the user had edited it. Our other guiding principle is we don't want anyone to lose work.

      We rejected solutions such as append the original text as we think that would cause confusion and end up with users submitting both.

      We also rejected displaying an alert when they are about to lose the value, as it's not obvious what the user should do to not lose their text and switch project.

      Instead, when a behaviour overwrites a field on project/issuetype change, the overwrite will happen but we will show a flag explaining what happened with the previous value(s), so the end-user can copy and paste whatever parts of it they want to retain.

      Please let us know if that won't meet your needs.

       

       

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tbatagiannis Thanos Batagiannis
              Reporter:
              jechlin Jamie Echlin
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: