I have a filter shared to a group, there are people in the project that cannot view the filter

[Mindy Johnson]

This is the filter we are using and the owner has shared it with the proper project so they should be able to see if.

due <= 5d AND project = SS AND issuetype in (standardIssueTypes(), Epic, "Research Spike", Story, Task) AND status in ("In Progress", "In Review", Open, Stalled) AND Sprint = 417 ORDER BY cf[10009] DESC, cf[11638] DESC, created DESC

the highlighted lettering is what the filter is stuck on for them.

The person that created the filter nor I encounter this issue.

Any suggestions?

Thanks
Mindy

~

UPDATE - I have reviewed all custom fields and cannot find the id -11638

[Trudy Claspill · Accepted solution]

Hello @Mindy Johnson 

What do you mean the users are "stuck"? Exactly what are the users seeing or experiencing when trying to use the filter?

You can use the following URL to access the Edit screen for a custom field when all you know is the field ID

https://<yourcompany>.atlassian.net/secure/admin/EditCustomField!default.jspa?id=#####

You will have to update the URL to reference your Jira instance, and replace ##### at the end with the numeric ID of your custom field.  The resulting screen will show you the name of the custom field.

[Mindy Johnson]

@Trudy Claspill  - thank you so much.

What I mean by stuck is that a few users cannot run the JQL.

She had to recreate the shared filter herself and then she was able to run the query.

I will try the url above and see what I can find.  Thanks again for your help!

[Trudy Claspill]

For the users that are having problems please elaborate on the steps they are executing to try to run the filter and the results that they get. Are they able to access the filter in the list of all filters? What happens when they click on the filter in that list? Do they get an error message? If so, what is the error message?

[Mindy Johnson]

@Trudy Claspill 

1. to to filters and find the saved filter

2. attempt to run it and this is the error that appears

3. if JQL is built directly in her instance and saved, the query runs perfect and returns results, but she cannot run someone else's shared query to return the same results.

I used the query provided about and found the cf[11638] is the ID for the EPIC.

Thanks Mindy

[Trudy Claspill]

Hello Mindy,

Thank you for that additional information.

What type of field is custom field 11638?

You said the user has to create the filter directly in her "instance" and then it works. Is the user accessing the same Jira Cloud site as you, or a different Jira Cloud site?

[Mindy Johnson]

11638 is the field for EPIC.

She is using the same cloud site as we are.

[Trudy Claspill]

The name of the field doesn't tell me what type of field it is.

When you go to the Custom Fields screen and find this field, what does it show in the Type column?

Example

[Mindy Johnson]

Epic = Epic Link Relationship

[Trudy Claspill]

I am still puzzled why the user is getting the error if they try to use the Saved Filter but not if they retype the exact same JQL syntax themselves.

Can you show a screen image of what you see on the Custom Fields screen when you have searched for and found that custom field (the one that has ID 11638)?

Your question is posted in the Jira Service Management Questions community. Can you confirm for us is the "SS" project a Service project or a Software project? That will be shown at the top of the navigation pane on the left just below the project name.

Is the "SS" project a Company Managed project or a Team Managed project? that will be shown at the bottom of the navigation pane on the left.

[Mindy Johnson]

Thank you Trudy for your persistence. 

It puzzled me as well and it has only happened with this filter.

1.  This is the results when locating cf 11638

2. SS is the project key
** project is company-managed
** project is categorized as a software project

[Trudy Claspill]

With the above you were able to find that the custom field name is "Epic".

What do you see when you the following URL (modified to use your instance URL) and search for the "Epic" field?

https://<yourCompany>.atlassian.net/secure/admin/ViewCustomFields.jspa

This is an odd issue. You might want to have your Jira Admin open a support case directly with Atlassian to see if they can find the root cause.

https://support.atlassian.com/contact/#/

[Mindy Johnson]

It shows me that the field is there.

Thanks for all your help, I couldn't figure it out either.