Jira REST API createmetada omitting Summary field for Site Admins

[Rachel Frazier]

Hello,

I am trying to look into an issue why Site Admins for this project are not seeing the "Summary" field appear in the list of fields from the response for the API that gets the create field metadata for a project and issue type id.

We are using the REST API to file Bug and Feedback work item types and have had no issue with this. We are now using the API to try to file Task work item types. When members run the API, "Summary" is listed in the fields; however, when Site Admins run the API, "Summary" is not returned in the list of fields. This is ONLY happening for Task work item types and not Bug and Feedback work item types.

I have already confirmed that the Screen backing the Task includes the "Summary" field via the Jira admin settings. I have also tried to set up a test Jira instance to see if I can replicate the issue in a different project, but the issue is not reproducible there, which leaves me to believe there is a setting problem somewhere. To be clear, the site admin is able to file Task items through the web page just fine.

I am at a loss for why Site Admins are not seeing a built-in Jira field that is included on the Screen in the response from the Jira REST API. Does anyone have any other information?

[Rachel Frazier · Accepted solution]

Just wanted to report back here that this was a bug in our library interfacing with the Jira REST API. We were not accounting for the totalResults/maxResults, so the maxResults was 52, but we were only looking at the 50 coming back, so "Summary" was one of the 2 missing. Adjusting our app logic resolved the issue.

[Tomislav Tobijas]

Glad you managed to resolve this @Rachel Frazier 

Thanks for sharing the solution 🙌

[Tomislav Tobijas]

Hi @Rachel Frazier ,

The only thing that comes to mind is trying to troubleshoot this by using "Find my field" (Show fields) feature in the UI. Although, as you said, the site (app) admin is able to see the field in the web interface and not via API.

Apart from that, permissions are the most relevant cause of these kinds of issues, but it's a bit unique scenario, so I'm not sure if it's up to that. Maybe... you could check workflow properties for Task as well 🤔

Also, things that can affect what you're seeing:

• Field config and screen assignment > you've checked that
• Field context > maybe also review config. there as well

Have you tried checking with Dev community if someone there has any insights? Potentially, this user could also reach out to Atlassian Support, and their staff should be able to help them troubleshoot the issue 👀

Cheers,
Tobi

[Rachel Frazier]

I haven't yet tried the Dev community. I'll check there. I've also confirmed this is impacting multiple Site Admins and not just one user in particular. It's something about the role "Site Admin" that's hiding the field.

[Rachel Frazier]

Just wanted to report back here that this was a bug in our library interfacing with the Jira REST API. We were not accounting for the totalResults/maxResults, so the maxResults was 52, but we were only looking at the 50 coming back, so "Summary" was one of the 2 missing. Adjusting our app logic resolved the issue.