Hi Supriya,
at itdesign GmbH we have at least twice developed an interface to Jira for our customers. The two interfaces have differed in the mapping of Jira issue types to the Clarity task structire.
The last ones, synchronizes tasks (issues) and actual time (workloads) from Jira to Clarity.
The mapping from the higly flexible and sometime customers specific Jira Issues to the Clarity WBS is a design issue which you should careful consider.
Invest some time in creation and runnig of test cases which tests what happends when you do issue type conversion in Jira (Story - Bug - Task - Sub Task ....).
If you transfer actuals/workloads, then you may face some issues depending on the mapping, as Clarity phases do no allow assignments/actuals.
On the technical part: we have used Java/Groovy Jobs which access directly the Jira over the REST-API and used mainly XOG calls for doing the Clarity import.
XOG may run into some limits, depending on your requirements, like having to change the task id in Clarity.
We have also used Clarity integration processes in the past to do it, but this may be to slow if you transfer/update many issues at once.
Let me now if we could support you with this, or if you got more questions.
Best regards,
Sergiu Gavrila
---------------------------
itd Assignment Editor - Effective Multiproject Resource Planning and Capacity Analysis