Is there any field that identify the source of bug on Jira whether internal or external?

[Hanan Nagy]

Is there any field  in the bug details that differentiate between the bugs reported internally from the QA team members and the external bugs reported from the site ?? I mean the origin of the bug?

[Max Foerster - K15t · Accepted solution]

Hi Hanan,

you will have to provide some more information for a better understanding and so we can provide you with a precise answer. So we're talking about Jira Software here? There is no difference in "internal" or "external" bugs unless you implement some kind of marker (custom field, label, component, suffix in the summary, you name it). Lots of this could also be achieved using workflow post functions (provided by third-party apps) with conditional executions (for example depending on the reporter of an issue). By "external" do you mean issues create from an issue collector in a project?

Best, Max

[Hanan Nagy]

first thanks for answering my Question

Second, yes I'm talking about Jira software

and yes I mean by external those who are working on the site itself - my clients

and now what kind of fields that should be added to bugs to differentiate between its origin? 

[Max Foerster - K15t]

Hi,

please don't mind me asking again but what do you mean by "working on the site itself". Your QA team members are user in Jira in a project, right?

How are your customers using Jira, accessing the project and creating issues?

And it is totally up to you how you want to differentiate between those "internal" and "external" issues. You could add a simple checkboxes custom field which just has the option "Internal" to check (or external). Whatever you like better. You have different kinds of custom fields available in Jira and can create and add them to screens them as a Jira administrator.

Best, Max

[Hanan Nagy]

to answer your Q first, I meant by external those guys who works at the client side to test our application there and they can log their found issues on Jira as well as my team.

Second I like the idea of adding custom field like radio button (Internal / external) in the issue to use it later in my queries to get this data.

but unfortunately I don't know how to make it as I'm new to Jira software

[Max Foerster - K15t]

Hi Hanan,

please have a quick look at this thread: I wanted to know if I could create a new field in a project

My comment there contains a link to the documentation of how to add fields and a second important link to the structure of screen and schemes in Jira. Reading through both links should answer most of your questions on how and where to create fields and how to use them in a project. If you still need assistance you can ask us here in this thread and we will try to help you. :)

[Jack Brickey]

If you are trying to identify the group that is originating the issue, e.g. DEV, QA, CUST then you could create groups, a custom single-select field and use an addon to assess if the creator is in membersof ("").

if this is what you are aiming for and need further assistance to make it happen JLMK.

[Hanan Nagy]

I need to identify the group who submit the bug if they are the QC team in my office or they are the guys who work on site who submit the bug and my team didn't catch it here

[Thomas Deiler]

Dear @Hanan Nagy ,

I assume you use JSD. So you can distinguish between internal and external, wehen assigning the users to a so called "Organisation". As soon al users are mapped, you quickly see the origin of an issue.

So long

Thomas

[Hanan Nagy]

Thanks for reply but where can I find the Organisation field - it would be better if u can provide a screen shot.

[Thomas Deiler]

In Jira Software - you do not have that bundled custom field "Organisation". This is shipped with Jira Service Desk.

[Hanan Nagy]

ok, thank you