-
Bug
-
Resolution: Low Engagement
-
Medium (View bug fix roadmap)
-
None
-
7.12.1
-
7.12
-
1
-
Severity 3 - Minor
-
0
-
Issue Summary
Custom Fields REST API call returns custom fields type incorrectly
Steps to Reproduce
- Run the following rest call:
GET /rest/api/2/customFields
Expected Results
As per the docs https://docs.atlassian.com/software/jira/docs/api/REST/7.12.1/#api/2/customFields-getCustomFields we get a results with the type as shown below:
{
"id": "customfield_10000",
"name": "New custom field",
"description": "Custom field for picking groups",
"type": "com.atlassian.jira.plugin.system.customfieldtypes:grouppicker",
"searcherKey": "com.atlassian.jira.plugin.system.customfieldtypes:grouppickersearcher"
}
Actual Results
{
"id": "customfield_10200",
"name": "My Select List",
"type": "Select List (single choice)",
"searcherKey": "My Select List",
"self": "http://localhost:7121/jira7_12_1/rest/api/2/customFields/customfield_10200",
"numericId": 10200,
"isLocked": false,
"isManaged": false,
"isAllProjects": true,
"projectsCount": 0,
"screensCount": 5
}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-19762] Custom Fields REST API call returns type incorrectly
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | Original: triaged | New: cleanup-seos-fy25 triaged |
| UIS | Original: 1 | New: 0 |
| UIS | New: 1 |
| Minimum Version | New: 7.12 |
| Support reference count | New: 1 |
| Priority | Original: Low [ 4 ] | New: Medium [ 3 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Component/s | New: Documentation [ 12975 ] |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center