Using direct URL without getting Error message?

[Linus Lindroth]

Hi I have been trying to utilize the tip on this page: https://confluence.atlassian.com/display/JIRA051/Creating+Issues+via+direct+HTML+links but the users come to an Error page which doesn't look nice.

Is there a way of getting to the proper login screen and after login to the "create issue" dialog with the right project and issue type selected? Currently I'm using this URL: https://<base url>/secure/CreateIssue!default.jspa?project=CR.

Or is there a way of modifying the Error message to say something else?

The catch is that the user might not initially be a JIRA user but will be after first login (using LDAP authentication with create user at first login checked) so I want to use the standard JIRA create issue form but without first getting to an Error page.

Note that the user might never have been in contact with JIRA and it doesn't look professional to see an Error page even if (in small letters) it tells the user to login.

JIRA Error using URL to create issue.png

[Steven F Behnke · Accepted solution]

@Linus Lindroth, I am currently using several links that contain arguments to the Project and Issue type only and they work fine. My example is as such:

https://jira.fqdn.com/login.jsp?permissionViolation=true&os_destination=%2Fsecure%2FCreateIssue!default.jspa%3Fpid%3D11301%26issuetype%3D10400

I think you should note, you NEED to properly escape ampersands, equals signs, and forward slashes after the os_destination section.

Something like this may help: http://meyerweb.com/eric/tools/dencoder/

[Linus Lindroth]

Hi Properly escape the special characters help so JIRA doesn't cut if out but JIRA still ignore my Issuetype parameter which is annoying. I have double checked that it is the right id I'm using. Any ideas why?

[Linus Lindroth]

Sorry it was a small misstake that I used Issuetype instead of issuetype. The capital letter screwed everything up. Thank you.

[Steven F Behnke]

No problem, I ran into the EXACT same problem with linking to a dashboard. Let me know if I can help further!

[Steven F Behnke]

Totally is! If you try to log in to browse something you don't have permissions to, you get this login screen instead of the error screen: 

image2015-3-2 18:52:33.png

https://jira.fqdn.com/login.jsp?permissionViolation=true&os_destination=%2Fbrowse%2FTEST

All you need to do is tack on your URL Encoded path onto the os_destination=  I've used this to a high degree of success for a "portal" for users who weren't used to JIRA, one click brought them to their issue type create screen.

If they are logged in it will redirect them right away, otherwise it will prompt them for login first.

[Linus Lindroth]

Thanks for the reply I don't fully get it, what do I put after the os_destination in this case? I tried with https://<base url>/secure/login.jsp?permissionViolation=true&os_destination=CreateIssue!default.jspa?project=CR but that doesn't work.

[Linus Lindroth]

Ok got it after some testing. It should be https://<base url>/login.jsp?permissionViolation=true&os_destination=/secure/CreateIssue!default.jspa?pid=10405 to work The /secure was in the wrong place

[Linus Lindroth]

@Steven Behnke Hi again, I ran into another problem now. When adding a second argument (for example the issuetype=10103) JIRA always cut them off?? I can't figure out why. I'm currently using https://[base_url]/login.jsp?permissionViolation=true&os_destination=/secure/CreateIssue!default?pid=10506&issuetype=10103&priority=3 Do you have any idea of how to succeed with multiple arguments?

[JamesT]

Not sure if you already figured this out, but I think you need to change the "&" characters in the os_destination value to "&amp;".

[Kyndra Morris]

Anyone having problems with their links working now?  Here is the link that I use.  

http://jira.corp.net/jira/secure/CreateIssue.jspa?pid=14202&issuetype=11600

Mine were working fine then we upgraded to a new version of DSTConnect and upgraded to a custom theme.  Now when I click the link everything seems to be working fine until I click on the Create button.  Then I get the following error message 'Please wait a moment for the server to finish then retry your action."  I can hit OK, but I am in an infinite loop.

If I create the issue from within JIRA, it works fine.  

We are on JIRA 6.4.12 and Confluence 5.9.11.  

[Kyndra Morris]

There is a new macro Insert JIRA Issue/Filter (choose Create New Issue) that should be used.  

New Create Issue MAcros.JPG

The issue that you may have is requiring fields that aren't on the same macro form.  See the error messages it is giving me on mine.