PROBLEM: The manager's tool of choice is Microsoft Project. Needless to say why. Everybody is happy with JIRA, but when it comes to understanding the WBS, scheduling and reporting,
things get complicated.
SOLUTION: To make life simple again, they introduce Ceptah Bridge. Manager creates a new project plan and pushes it to JIRA. Team members receive their assignments and split them into sub-tasks, as they see fit. They also enter their time
estimates. Then the manager imports the new sub-tasks and estimates from JIRA, which adds another level to the project structure, and schedules the activities. After that
the systems get synchronised so that the team can start working on the issues. As they log work and enter remaining effort, the manager pulls the actuals from JIRA and
re-schedules the tasks, if required.
PROBLEM: The team has always been using JIRA, but the company management wants to see reports in Microsoft Project.
SOLUTION: The team leader extracts the necessary information from JIRA using Ceptah Bridge to prepare the reports.
PROBLEM: A huge project portfolio stored in Project Server or Project Online needs to be kept in sync with issues in JIRA.
SOLUTION: The IT team sets up an automated task that runs the Ceptah Bridge command-line tool on schedule to make sure that the changes
made on each side are brought across.