Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-42108

javascript error - Uncaught Unable to find either an issueId or projectId to submit the attachment to

    XMLWordPrintable

    Details

    • Introduced in Version:
      6.03
    • Symptom Severity:
      Severity 3 - Minor
    • Current Status:
      Hide
      Atlassian Update – 28 May 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 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 – 28 May 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 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

      Description

      Currently, AUI forms with a file input seem to need an 'id' attribute to stop a runtime javascript failure that breaks all other scripts.

      Lack of an 'id' element, or adding with/without a value but not being a valid issueID/projectID results in a javascript console error:

      Uncaught Unable to find either an issueId or projectId to submit the attachment to.

      Odd behaviour then occurs if there is already an 'id' form attribute on submit that, a new file picker element dynamically injected, with some related text, which is not desirable.

      1. This requirement is asserted on all forms but should only apply to JIRA forms with a specific class selector for the cases that need it (there isn't one)
      2. Usage of 'id' with no prefix is an undocumented requirement for forms with file sections. 'id' is too generic, and is likely to be already used, and should be something else, 'relatedIssueOrProjectId' for example. If this script targeted applicable forms appropriately, the use of 'id' or not would not matter
      3. The related script should detect lack of presence of a more appropriately named required attribute rather than breaking

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            andy11 Andy Brook
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: