RELATED IDEAS
Ability to map constants to custom fields in Github
Who would benefit? |
Anyone with a Github integration |
What impact would it make? |
Right now, the only way to prevent unhandled errors is to research the backend technical ID's and map those as constant values to send choice values over as a constant to a Github custom field. This is not an easily available workaround. |
How should it work? |
Users should be able to input the human-readable choice values as constants in field mappings. |
It would be great if any future implementation could be backwards compatible. Those of us who have invested time in identifying and using the IDs in integration mapping will be thankful if existing mapping of those IDs isn't broken when support for the corresponding human-readable values is added.