Nikos Kleidis
Not having a CRUD API to add a new option to a Dropdown Custom Field, is creating the need for manual steps in our automatic pipeline.
To get an idea of what we are trying to achieve. When we want to publish a new version of our app, we want to tag each ticket that was implemented with the new version number so that we know all the tickets that were implemented in that version
Our desired pipeline consists of the following steps:
1) run
npm version minor
to create the new version2) get the new version number from the package.json (e.g. 1.42.0)
3) Using ClickUp API, create a new dropdown option (1.42.0) for our "App version" custom field
4) find using git all the commits that were implemented since the last release and extract all the ticket numbers mentioned in them.
5) Apply the dropdown option created at step 3 to each ticket of step 4
Unfortunately, currently step 3 is not possible. What we currently do is to manually create a new dropdown option for our "App version" CF and then running the script which instead of step 3, it tries to find the dropdown option with text 1.42.0 using the ClickUp API "Get Accessible Custom Fields". If the option is not there, the whole script fails