Hi,
For our bug monitoring view (we use Kanban boards), I would like to display the "Reporter" field so the developers know who to contact for further details easily.
However, I cannot manage to display it in the view.
I have added it in my Screen configuration:
And tried to customise its disposition:
But when I open the issue, I do not see anything:
When I look in my Issues explorer, I see that all the "Reporter" fields are marked as "Unassigned" :
Does anyone have an idea on what's going on? Permission issue (I'm a JIRA admin on this platform but maybe I missed something?)? Other?
In the Default field configuration of my organization, the "Reporter" field was tagged as hidden, which was the cause of my problem. :-)
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 should be there OOTB. How are the issues being created (portal, email, Create button). The fact that it shows not assigned tells me that it is not getting filled in at creation which is rather odd as that should be automatic. It would be interesting if you created a test issue to see if you are listed as the Reporter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also do all issues have not assigned in the Reporter field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I create them from the "Create" button".
And yes, no issues have any value in the "Reporter" field :/
The issue on the screenshot is a test issue I've just created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First I generally recommend against using the create button. The reason for this is that some things can get missed such as the request type which is important if you want customers to be able to view an issue in the portal. Rather as an agent, use the raise request button.
with that said, when you do create an issue on behalf of a customer you should see the following. If yo do not change it the you, as the creator, will be the reporter.
please share what you are seeing. Is it possible that someone created a custom field called “reporter” resulting in this issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I do not have a "Raise request" button in my view:
I see that this tool added tags as "jira-service-desk-cloud".
We only use the Jira Software Cloud I think
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok hold on. This post is under the JSM collection so I think we are off track here. Looking at your image it appears that indeed this is a SW project. So forget all of the previous input and let’s reset.
The one bit of previous input that should still apply is that the Reporter should be there by default. That is, when created, an issue will have the Reporter set to who created the issue. It makes no sense that this field would be empty unless there was some automation that clears the field. While this would be very strange I would certainly check that. I would be interested in whether this happens on other projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hum, sadly no automation rule mingles with the Reporter field (either on the project or the global level), or it's a secret one!
I agree that this field should appear & fill itself automatically!
Thank you for your time!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I recommend reaching out to Atlassian support. I’ve never seen this field not be populated at creation. So if you don’t have a custom field called reporter that could explain things then something else is amiss.
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.
Report back here when you get closure if you don’t mind.
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.