In COR we have the possibility to integrate our Jira account and automate the creation of users, projects and tasks within COR.
Within COR Configuration section, we will find the "Integrations" tab and in Available Applications, we will be able to visualize the Jira option.
When clicking on "Connect", a new modal will appear with the fields to complete in order to associate our COR account with Jira.
In the first field, we must enter the email with which we access our Jira account, but it is essential that our user has Administrator permissions so that the integration can be successful.
In the second field, we must paste the URL of one of our boards, so that COR can identify the JIRA product to be connected.
In the second step, we must paste the API Token generated in Jira and then click on "Connect".
When finished, a confirmation that COR has connected to JIRA will be displayed:
There, we must click on "Create API token", assign a label (title) for our connection to COR and click on "Create". This will give us a token that we must enter in COR, which we can visualize by clicking on the eye icon and copy by clicking on the "Copy" button.
Note: We will only be able to visualize and copy the token at the moment of creating it, therefore, if we close the modal before copying it, we will be able to remove it and create a new one to make the connection.
In order for new users in JIRA to be created in COR, it is necessary to set their email address as public in JIRA.
To do this, that person must go to their JIRA Account Settings > Profile and Visibility and in the Contact section select "Anyone" under "Who can see this?" in Email.
If this address is private in JIRA, it is not possible to create the user in COR.
Additionally, if the visibility of the email is not changed to " Anyone ", even if the user already exists in COR, the users will not be listed as responsible for their projects and tasks.
When connecting JIRA with COR, an integrator client will be automatically created, to which all projects created from JIRA will be assigned. Additionally, all projects created in JIRA will have by default "today" start date, end in one month and 160 estimated hours.
The client, as well as the start/end dates and estimated hours, can be changed later from the project edition.
All tasks created from JIRA will be assigned the COR status corresponding to the standard JIRA status:
- To Do > New
- In Process > In Process
- Done > Finished
Customized Jira statuses will always appear in COR as "In Process".
All tasks created from JIRA will be assigned the COR priority corresponding to the standard JIRA priority:
- Highest > Urgent
- High > High
- Medium > Medium
- Low > Low
- Lowest > Low
Custom priorities in JIRA will be listed with "Medium" priority in COR.
Unlike COR, JIRA assigns a single responsible (Collaborator) per task. If we modify the responsible for an issue in JIRA, this will replace the collaborators that have the corresponding task in COR.
Note: If previous collaborators were working on the task in COR, they will still have suggested hours even if they have been removed from the task.