Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-28116

Assignee field repopulates AJS.params on every keypress

XMLWordPrintable

    • 5
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 December 2017

      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 Time 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 Jira 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 Atlassian Bugfix 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.
      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 06 December 2017 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 Time 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 Jira 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 Atlassian Bugfix 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. Thank you, Ignat Alexeyenko Jira Bugmaster

      In AssigneePicker.js it looks like the url function is recalculating the assigneeEditIssueKey value on every AJAX request:

      //reset the assigneeEditIssueKey param, so that when we go from an quickedit dialog to a quick create dialog for
//example the value isn't set!
AJS.params.assigneeEditIssueKey = undefined;
AJS.populateParameters();

      This should only need to be done when the control is initialized, so it could move out to the AssigneePicker's init method.

      However, if a param is being set per-control and not per-page it indicated that the data should be attached to the control and not use AJS.params. I'd recommend adding a data-issue-key attribute to the assignee field's <select> element via a single-element Map passed from the assigneeField.soy template to the singleUserPicker.soy template.

      That way you could have two of these fields on the same screen and not have them clash with one another. Frother knows what I'm talking about : )

          Form Name

            [JRASERVER-28116] Assignee field repopulates AJS.params on every keypress

              Unassigned Unassigned
              dtaylor David Taylor (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: