Details
-
Bug
-
Resolution: Timed out
-
Low
-
None
-
6.3.15
-
6.03
-
Severity 3 - Minor
-
-
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.
- 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)
- 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
- The related script should detect lack of presence of a more appropriately named required attribute rather than breaking