As you may know, Atlassian is decommissioning the External Asset Platform at the end of the year. We are utilizing Forge Custom Fields to replace Jira’s CF. So, we had to think of a migration process like fetching customers custom fields, their configurations and linked values. Then creating Forge CF with values. By the way, we are not migrating our app to Forge natively, we are only adopting forge. Migration process will be run on connect app. However, we cannot update Forge CF from a connect app as stated in the document.
Connect apps cannot access this REST resource.
Should we implement that step in Forge or do you have any other recommendation?
Can I use appUserToken or appSystemToken to access the REST API?
Given this API can be accessed by Forge, that means that Forge Remote would also have the ability to use it. This would enable your existing remote Connect service to interact with the API utilising the remote token provided by Forge. Is this activity something which would occur once off (i.e. when a customer is migrated to Forge), or based upon a customer request?
I really appreciate your answer and sorry for replying back so late. We have been very busy with replacing Forge with External Asset Platform.
We have found a workaround and utilized edit issue endpoint to update Forge custom fields value. However, we face 429 errors and it makes us to wait which is something we don’t want for our customers.
So, Forge endpoint seems more efficient in terms of 429 as it allow us to update multiple issues at once(please correct me if I’m wrong).
I will be testing appSystemToken but in the meantime, I have a question about the token. I noticed that the expiration time is 4 hours. Can we change it or can we rely on refreshing it in every 4 hours?
You can associate this to an hourly timed trigger, meaning you’ll refresh more often and each of those tokens would have a TTL of 4 hours. With that said, the maximum lifetime of these tokens in 4 hours.
