-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Integrations
The data retrieved to generate Development Summary from FishEye:
/rest/dev-status/1.0/issue/summary
contains the full / unbound list of commits together with the number of commits. Seems the list of commits is redundant as only the number of commits is shown.
{
"targets": {
“PROJA-2": [
{
"type": {
"id": "repository"
},
"count": 1,
"objects": [
{
"lastUpdated": "2016-01-11T14:37:04.000+0100",
"count": 7004,
"commits": [
"a01c7cd2ca0a3bce75d2cc0ecb6656c91515b93a",
"dfac50afbe5158f3d69b4761af1145cf7a8d41e3",
----7000 entries----
"3b805eedd8e39dce42d603577e3f51c34e2e1dc2",
"106753f42fbdcfa5d84552c7c4e0f899f5daa357"
],
"type": "git"
}
]
},
{
"type": {
"id": "review"
},
"count": 1,
"objects": [
{
"lastUpdated": "2016-01-11T18:20:12.437+0100",
"dueDate": "2016-01-18T14:30:00.000+0100",
"state": "REVIEW"
}
]
},
{
"type": {
"id": "branch"
},
"count": 0,
"objects": []
}
]
}
}
Large response is causing the following error in JIRA:
json for issue * is too big its size is *
and causing data not being cached.
For the detailed view:
/rest/dev-status/1.0/issue/detail
the response shows all responses on a single page which for large data sets is causing poor UI responsiveness.
- is related to
-
FE-5652 getReviewsForChangeset() can be very slow for large changesets
-
- Long Term Backlog
-
- relates to
-
- Closed
- mentioned in
-
Page Loading...