I use Jira CLI - runFromCsv, however I can't update Jira fields that are not available on the appropriate screen. It gave the following error:
Client error: 'testField' is not a defined field or is not valid in this context (for instance, not being available on the appropriate screen).
However I can do the update using Jira External System Export GUI. Also I can't bypass some workflow rules using CLI, but I can using the Jira External System Export GUI. Is there any suggestion on how to bypass these Jira rules using CLI or RestApi?
A use case is to sync any fields changes from other tracking system to Jira. This is needed after we cut over to Jira and during the transition we want to keep both data in other tracking system in sync with Jira.
These processes are respecting the rules you have set up in the application.
CSV import can bypass them because it's there to create data, not transition or edit it.
If there were a full way for a user to break the rules, it would make no sense in having them. If you set up your JIRA to prevent me doing X by clicking, then you absolutely need to stop me doing X in a script.
Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot