We are setting up direct HTML (customer links) for repetitive requests. We've worked out most of the URL we just can't get the reporter part to auto-fill with the current user.
Ex: https://jira.corp.xxxxx.com/secure/CreateIssueDetails%21init.jspa?pid=xxxx&issuetype=7&summary=xxx&assignee=xxx&priority=8&reporter=admin
When we use "admin" it auto-fills our Jira Admin, not the current user. We've tried "currentuser" as well.
just in case you have not seen the specific part in documentation for "Reporter" I wanted to add that there is some speciality:
To have the reporter field default to the currently logged in user, the user must be logged in and must not have the
Modify Reporter
permission.
So I think you could leave out the "reporter=admin" part and let Jira do the rest (automatic) but, indeed, it would require that the user "does not have the modify reporter permission" (as per documentation).
Edit: I forgot to link the documentation:
https://confluence.atlassian.com/jirakb/how-to-create-issues-using-direct-html-links-in-jira-server-159474.html
Regards,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How is your html reaching into Jira to work out what the user id of the current user is?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The reporter field needs to be given a user id. I was guessing that your application that is building the url needs to ask Jira for the user's id.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh. We are putting these together from scratch. No application is being used. Though, are there any good recommendations?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't know, I don't know what you are trying to achieve here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Our end game is to set up Jira links that will populate the required information our stake holders may not know or understand about our project. All they would need to do is add a summary and description to the ticket and submit. Right now we do not have access to any sort of program that will accomplish this for us so we decided to build it ourselves.
We are just running into a blocker concerning “reporter”.
Hope that helps clarify our intent. :P
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It does, a bit, I think the next thing to look at are probably "issue collectors" - that's code you can add to non-atlassian sites to pop up questions for your users when they get stuck (but I don't want to rule out more things, or stop the conversation here - if these don't work, there is a lot more to look at)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not sure the "issue collector" will fit our needs. All reporters are internal. I can't see how I would be able to pre-populate the information. However, I do see potential if we can figure out how to add required fields and pre-popular with the required information to submit a ticket.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
An issue collector will try to use the reporter's Jira account for reporting the issue.
Using an issue collector would bypass the need to pre-populate anything, as you could set it to use an issue type where you've already defaulted all the data you want to pre-populate on issues coming in that way.
Going back to the original question though, I'd question the method you're using for repetetive requests - could you not automate them with a service or external REST calls?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's the only option currently available to us. So we kinda MacGyvered it.
I'm not sure if we have access to services like that within our org. Is there any I can request our Jira team to look into?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Cloud has automation built in, so you could look to using that for some of of what you want to pre-populate when you create new issues. The REST API is always available to you as well, no need to ask the admins if it's there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- BTW. Thank you so much for your help. This has been a journey.
Can you share any tutorials or guides on how to use the built-in tool? I'm guessing it's the "issue collector" you previously spoke about.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.