If you are setting up Jira addon integration with iObeya via OAuth 2.0 protocol and your company has implemented security components in your network frontline (DMZ/proxy/firewall) , please consider these tips:

• DMZ Compatibility: make sure your DMZ configuration supports OAuth 2.0
• Firewall and Ports: Allow traffic through necessary ports (usually 80 and 443).
• Proxy: Ensure proxies don't prevent Jira-iObeya communication.
• User Permissions and scope: Ensure user accounts have admin privilege in Jira and iobeya
• Client IDs and Secrets: Ensure that the client IDs and secrets used in the OAuth 2.0 flow are accurate and match between Jira and iObeya.
• Redirect URLs: Verify that the redirect URLs specified in your Jira and iObeya configurations are correctly configured and accessible from your DMZ.

By following these steps, you'll facilitate the communication between Jira and iObeya.

It is possible that a Jira project will change its name, its key or its workflow. If it is used in iObeya, what are the impacts and how to manage them?

Warning: To avoid any problems, we recommend testing beforehand on a test project

1°) Change of key

Impact : The jira cards are considered archived and therefore no longer linked to the project.

Actions to be taken:

• Reconfigure the Jira tool set in the docks
• Do a mass import to recreate the cards.
• Delete the cards with the old key

Related documentation :

• Configuring a Jira tool set
• Bulk jira import 

2°) Change of workflow

• Special case of the Kanban board :

Impact : The board being based on the workflow states, we do not benefit from the changes on the iObeya side (more or less states, name changes, etc)

Action to be taken : The board must be recreated in order to use the new workflow

Related documentation : Create a Kanban board

• Other cases : For any other case, you just need to update the jira cards.

Related documentation : Update jiras cards

3°) Change of name

If there is only a name change, the only impact will be in the name of the board, once entered in (top left).

Unfortunately, to correct this, the only possibility is to recreate the board.