I am trying to share a custom filter and when selecting Group, from Add Shares, the dropdown listing the groups is extremely limited, listing 9 of 51 groups.
Currently running JIRA 5.2 but this has been apparent since 4.3.2 (our last upgrade).
Any direction would be much appreciated.
Screenshot: Showing the small list of groups selectable from the Sharing Filter screen
Screenshot of all Groups
You are able to see only limited groups while sharing the customfield filter because you're the member of only those limited groups which you can see and not the list of other groups you mentioned in the screenshot. Just add yourself to the other groups and then check whether the remaining groups are getting displayed under the select list while sharing the filter.
Hope this helps!
Agree with @Steven Lam4 and @Konstantin Boyko that as a Jira system admin when creating a filter and providing access to the filter for a Jira (Atlassian application) group that I should have access to all the groups regardless of whether I, as the Jira system administrator, am a member of the group or not.
The general model of Jira is that the Jira system administrator has global access at all times and the group selection for the Filter permissions does not match the Jira standard (Atlassian application standard too since I own multiple Atlassian applications).
As I have an Atlassian Premiere Support contract I have filed a ticket with Atlassian to look into this issue which seems to be a functional bug if not an outright programming bug.
Note: you will not be able to see the ticket but including here for completeness:
Here's the reply from Atlassian:
On Thu, Jun 28, 2018 at 6:26 PM Tim Evans <email@example.com> wrote:
Tim Evans commented:
It looks like the ability for an administrator to share with all groups is being looked at as a functional improvement rather than a bug.
There is a long history and most of that is shown in the feature request, JRASERVER-15900
It used to be possible for the admin to share with any group but that changed. The JIRA product team reviewed this and after considering all factors it was decided that this would be classified as a suggestion or feature request, rather than a bug or regression.
We are making improvements to filters and groups and are tracking that work in JRASERVER-17783.
We are working with the JIRA product team regarding JRASERVER-15900and will send over more details when we have them.
Tim | Atlassian
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG