-
Suggestion
-
Resolution: Unresolved
-
1
-
15
-
Problem Definition
In Jira Software, Core, and Service Management projects, the "Domain of Reporter" and "Domain of Assignee" (advanced custom fields) are only shown in the OLD ISSUE VIEW, not available in the new issue view, even though populated.
Suggested Solution
This type of field should have its value shown also in the new issue view. This is how it looks like in the Old Issue View:
Why this is important?
This field is often used to store/validate the domain of Reporter/Assignee through an automated feature since the field is automatically set when setting the Reporter/Assignee field.
Workaround
Currently, there is no workaround.
- duplicates
-
- Gathering Interest
- relates to
-
JRACLOUD-74153 Custom field of type Domain of Reporter not showing in the new issue view
-
- Closed
-
- mentioned in
-
Page Failed to load
[JRACLOUD-74348] Domain of Reporter/Assignee type fields aren't available in the new issue view
I am amazed that this bug it still here and not fixed. In many service desk, specially when dealing with suppliers, the first thing the agent want to know is with whom they are talking. This was such a great field to classify tickets quickly, I find it more amazing that you leave such an obvious bug without fixing, where the field is visible in the issue navigator and in the queues.
You even promote an automation that makes use of this field for creating automatically organizations and sorting users, but you cannot see it...
As per this comment I am closing this ticket.
If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it as needed.
I believe this issue is a duplicate of JRACLOUD-61425: Allow to Search By Domain Name For Reporter Field
I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone thinks both issues should continue to exist. Thank you!
I believe this issue may be a duplicate of JRACLOUD-61425: Allow to Search By Domain Name For Reporter Field
Followers of this issue may be interested in the automation-based workaround suggested here.
This was removed to "protect user's privacy" according to Parolini's link, but now, not only is it hard to vet a user's email domain, but any workflows for specific customer relationships are impacted because JQL queries are now deliberately broken. E.g., if XYZ Corp was using Jira Service Desk, and when they receive a request from any email address from @ABCVendor.com it is supposed to receive elevated priority or some special sort of flag by contractual obligation, now this is broken. How is this supposed to be handled now?
Support of Domain of Reporter field has been removed as of 10/01/2021.
Would be lovely to have it there for the Servide Desk Projects, grouping and reports!
Thank you for your engagement on this ticket. We've observed that the Domain of Reporter/Assignee field types are rarely used and have made the decision to prioritise other improvements in the short-term. We will leave this ticket open for you to provide further context and will continue to monitor this ticket for updates and will let you know if we are able to prioritise it.
Agreed with Lara. We need this field in Service Management to quickly find requests from the same domain.