We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-40843

File Attachment information is getting carried over on subsequent issue creates.

      If the user creates an issue with an attachment and then attempts to create a subsequent issue (without an attachment), they get an error stating, "Temporary attachment not found. Session may have timed out before submitting the form".

      It looks like the file attachment data is getting carried forward from the previous issue. It appears this only occurs if the user opens the Create Issue form by right clicking on the "Create Issue" button and choosing the option to open it in a different browser tab (See Step to Repeat below).

      Steps to Repeat:

      1. Create the first issue (with an attachment):
        • Right click on the "Create issue" button and choose the option to open it in a different browser tab.
        • Fill out the necessary fields on the new tab, attach a file, and submit the issue.
      2. Attempt to create the second issue (without an attachment):
        • Again, right click on the "Create issue" button and choose the option to open it in a different browser tab.
        • Go to the new tab and view the Attachment area. Notice the file attached to the previous issue is listed (For the purpose of this test, don't uncheck it).
        • Fill out the necessary fields and submit the issue.
          RESULT: The following error is thrown: "Temporary attachment not found. Session may have timed out before submitting the form"

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-40843

            File Attachment information is getting carried over on subsequent issue creates.

                If the user creates an issue with an attachment and then attempts to create a subsequent issue (without an attachment), they get an error stating, "Temporary attachment not found. Session may have timed out before submitting the form".

                It looks like the file attachment data is getting carried forward from the previous issue. It appears this only occurs if the user opens the Create Issue form by right clicking on the "Create Issue" button and choosing the option to open it in a different browser tab (See Step to Repeat below).

                Steps to Repeat:

                1. Create the first issue (with an attachment):
                  • Right click on the "Create issue" button and choose the option to open it in a different browser tab.
                  • Fill out the necessary fields on the new tab, attach a file, and submit the issue.
                2. Attempt to create the second issue (without an attachment):
                  • Again, right click on the "Create issue" button and choose the option to open it in a different browser tab.
                  • Go to the new tab and view the Attachment area. Notice the file attached to the previous issue is listed (For the purpose of this test, don't uncheck it).
                  • Fill out the necessary fields and submit the issue.
                    RESULT: The following error is thrown: "Temporary attachment not found. Session may have timed out before submitting the form"

                        Unassigned Unassigned
                        2528af6bdebe Guy Anela
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            2528af6bdebe Guy Anela
                            Affected customers:
                            0 This affects my team
                            Watchers:
                            2 Start watching this issue

                              Created:
                              Updated:
                              Resolved: