Help creating a mini URL for an issue screen?

[Phil]

Hi all,

I'm currently trying to create a mini URL to share with my wider team to enable them to make requests for enhancements on our product. I would like to ensure the reported by field defaults to the currently logged in user, however, I'm not sure what extra field values I need to provide in order to enable this e.g. reporter=?

Could someone please help? 

Also, is there a way to restrict the number of fields the user needs to populate on this create issue screen or is this just something to configure on the fields side for that given issue type?

Cheers in advance,

Phil

[John Funk]

Hi Phil - Welcome to the Atlassian Community!

By default, the reporter should be populated with the current user. Is that not happening?

Second, yes, you can modify the Create screen to have a smaller number of fields for the user to see. 

[Phil]

Thanks for your response, John.

1. I can't seem to get the reporter field to default to the current user. In the direct html link that I've created for this issue screen, I've even taken 'reporter=' out of it and yet it still informs me that the reporter field needs to be filled in before you can make a request. Is there standard logic I should be entering into the direct HTML link to ensure it defaults to the current user as the reporter?
2. Cheers - can you limit the number of fields directly in the HTML link or will I need to go and update the screen configuration fields for the request for enhancement issue type?

Phil

[John Funk]

Hey Phil -

1. You might try reporter = currentUser()

2. I would suggest you modify the screen configuration.

[John Funk]

You also will want to review this article if you've haven't already.  :-)

https://confluence.atlassian.com/jirakb/creating-issues-via-direct-html-links-159474.html?_ga=2.146340791.2091706550.1563133864-1082435282.1542634250

[Phil]

Thanks John. Unfortunately, your solution in 1 doesn't appear to be working for me. Also, I have seen that page to direct HMTL links, but it only suggests the following: 

On the second point, I've just realised that the team have a default issue type screen configuration for all issue type requests (whether it's to do with creating a new issue etc)... Without messing with that (just yet) is there a way to associate a new screen scheme to just the Request for Enhancement issue type in my specific project and have that layout present in the html link for creating an issue?

Sorry for the bombardment of questions - just trying to get as much of an understanding as possible.

Cheers

Phil

[John Funk]

No worries with the questions - bombard away.  :-)

You can create a Context for each field that you want show up just for your Issue Type.

Go to the Custom fields link, then click Configure next to the field on the far right hand side. 

Then at the top left side, click on Add new context.

Give it a name in the Configuration scheme label field at the top. 

Then select Request for Enhancement issue type. 

You will need to do this for each field you want on your screen. 

It's a lot of steps, but the best solution is you don't want to create a new screen scheme or modify the default. 

I hate that the Reporter thing is not working for you. Are you using Server or Cloud? 

One work around might be to always set the reporter to you, but then in a Post Function on the Create transition, set the Reporter to the Current User. 

[Phil]

Cheers John - I'll give this a go and get back to you.

Yes, the reporter issue is annoying - We appear to be using JIRA server.

[Phil]

John, once I have created the custom fields and associated them with the default team issue type scheme...can I then create a new screen specifically for RFEs and leave the default issue type screen associated with the other issue types? 

I'm just keen to not start moving field types around on the default issue screen.

Cheers for your help.

Phil

[John Funk]

Hey Phil - Absolutely, that is what the Issue Type Screen Scheme is all about.  :-)

Take a gander here:

https://confluence.atlassian.com/adminjiraserver081/associating-screen-and-issue-operation-mappings-with-an-issue-type-970609045.html

[Phil]

Cheers John.

I'll work on this and just ensure I get labelled as reporter for now.