Fixed
Nader Hadji GhanbariJanuary 24, 2018 at 1:59 AM
It seems that the issue key is still the only field not having the `fieldId` in the changelog. This little inconsistency means we have to treat issue key differently almost everywhere.
Is there a plan to fix this?
Nader Hadji GhanbariAugust 21, 2017 at 12:31 AM
It seems that the only field without a `fieldId` in changelog is the issue key, for instance when we move an issue to another project. This forces us to make the `fieldId` optional. Shall I create an improvement for this? Is it intentional?
Dave MeyerJune 21, 2017 at 6:33 AM
There are no plans for this right now @Tobias Anstett (K15t).
Tobias Anstett (K15t)June 21, 2017 at 6:32 AM
Will it also be shipped for server?
Nader Hadji GhanbariJune 21, 2017 at 6:31 AM
Great news.
Thanks a lot,
this will make our life easier. We can already remove a lot of code
As a Connect add-on vendor we receive a lot of `issue_updated` and we rely on the `changelog` to infer changed fields. The `changelog` only has the name of the custom fields (and apparently even some of the standard fields, like Components).
It would be great to have a more consistent API by providing id for all fields.