Revamp your productivity with action card alerts and Jira OAuth 2.0 support
The version 4.17 is a Cloud version. Therefore, the improvements and new features described below are only available for Cloud customers yet.
Of course, they will be available in the next certified version of iObeya for on-premise installations scheduled for Q4 2023.
QCD add-on (Enterprise plan)
This is an add-on that need to be installed and activated on your iObeya platform. If you can’t find it, you need to request to your platform administrator to activate the QCD add-on.
Improved Due Date visibility on QCD Action Card
Until now, when an action card was past its due date, there was no visual indicator to warn the users that the action was late.
We have improved the due date visibility on the QCD action cards with 3 differents states:
1. if the action’s due date is more than 2 days, then the due date field is white;
2. if the action’s due date is at less than 2 days, the due date field becomes orange;
3. if the action is past its due date and it has not been resolved, then the due date field turns red.
This will help you identify priorities regarding your opened action cards, whether you are looking at a Kanban board, in the QCD action plan or an action table on a QCD board.
These are add-ons that need to be installed and activated on your iObeya platform. If you can’t find them, you need to request to your platform administrator to activate the Agile add-on, Jira connector and/or the Azure DevOps connector.
Supports OAuth2 connection on Jira DC/Server
Atlassian, the company behind Jira, recommends using OAuth (Open Authorization) as a secure and efficient way to integrate with Jira’s REST API. OAuth protocol allows third-party applications like iObeya to access protected resources on behalf of a user, without requiring them to share their login credentials.
We announced beginning of the year that the Jira connector for iObeya was now compatible with the version 9 of Jira Data Center (i.e. Jira DC). We pursue our effort to better support large organizations that made the choice of Jira DC, and we are happy to announce that the new version of the Jira connector offers support for both OAuth 1.0 and OAuth 2.0.
This was made possible since Atlassian offered full support of the Jira’s API services that are required by the Jira connector when using OAuth 2.0. Beware, if you want to use OAuth 2.0 authentication, you will need to be on Jira 8.22, or Jira 9.0 as minimum versions.
We’ve added a new article on our FAQ to make it easier for you to understand which version of OAuth you can use depending on your Jira version.