Jira Connector For SAP Solution Manager Focused Build

Jira Connector for SAP Solution Manager Focused Build

While Jira is certainly one of the best sets of tools out there now, it often pays to have a good look at how it can be improved. With the connector, users will be able to see a backlog view that details your task Status, Assignee, Reporter, and Priority from your Focused Build or Jira. It also has a bi-directional mapping for creation from the Jira Board or Focused Build or Scrum Board.

In this article we’ll be primarily concentrating on the improvements brought on by Jira Connector for SAP Solution Manager Focused Build – so there’ll be plenty of complimentary functions discussed!

1 Jira Connector for SAP Solution Manager Focused Build at a Glance

 

Jira Connector for SAP Solution Manager Focused Build has a similar construction to our other Connectors. Every established connector provides an out-of-the-box solution that enables bi-directional integration between SAP Solution Manager Focused Build and Jira. With the connector enabling bi-directional mapping the Jira project can continue without a delay to the development team, however, you also build the connection to SAP Solution Manager Focused Build. Providing a complete single source of truth for your SAP and Non-SAP Environment.

Work can be easily tracked through a Backlog View and you guarantee everything is up to date through Synchronized workflows with Bi-directional mapping for creation from the Jira Board or Focused Build or the Scrum Board. In backlog, you can detail your tasks Status, Assignee, Reporter, Priority, etc from your Focused Build or Jira. Managing teams becomes easier with the CoreALM as the Jira Connector is a turnkey solution with a very flexible dynamic mapping of different issue types, status, and fields between SAP Solution Manager Focused Build and Jira supporting different use cases.

What we’ve built is a system that ensures that the management of Work Items within a project (Boards and Backlog) and the real utilization of SAP Solution Manager as a single-source-of-truth can be tracked, updated, viewed, and owned by everyone from Product owner to Developer.

2 Board View

  • The Board section contains the
    • Project
    • Board selection
    • Backlog View Menu

From here you can create

  • Tasks
  • Stories
  • Bugs
  • Epics

Once created you can update the status of any User story or epic by drag and drop or by opening the card and updating it as needed.

3 Backlog View

Every Product Owner or Scrum Master has one Backlog View per Epic/Project, any number of Sprints, and issues as designated by the team. The backlog view details your tasks from your Focused Build or Jira:

  • Status
  • Assignee
  • Reporter
  • Priority, etc

The Backlog View is maintained through a synchronized workflow with Bi-directional mapping for creation from the Jira Board or Focused Build or the Scrum Board.

The View details count of Stories/Tasks/Epics/bugs per Sprint. Further details on Date, SAP or Non-SAP, title, and sprint dates are all presented. With the option to further open the card and see the rest of the information on the card.

4 Simplicity

Jira Connector for SAP Solution Manager Focused Build board does not have the level of complexity available within the Jira board itself. However, what customization there is, is set up in minutes with dynamic mapping of different issue types, status, and fields between SAP Solution Manager Focused Build and Jira supporting different use cases.

We can create Requirements and WPs and WIs from Jira Epic by selecting the option to create in SAP and this will do the synchronization and create a user story in Jira and corresponding WI in SAP. With this Connection we can view in CoreALM Scrum board the Jira Board and the Jira Backlog, also we can create Jira issues directly from the CoreALM Scrum board.

5 Jira alone does not give you the whole picture

The main problem with Jira on its own is the lack of insight provided to leadership on a holistic level. With Jira, you are isolated in your view of that environment. The connector allows development teams to use Jira during the build phase while all parts of the requirement to deploy the process remain in SAP Solution Manager. For the User Story and Epic Jira will be the leading systems, which means the status is changed on the Jira side and synchronized back to Solution Manager to update the status of the Work Item and Work Package. Every aspect of the Connection is meant to be scalable and have a minimal business impact on production work, while immediately giving you insight into your SAP and Non-SAP Project Progress.

6 The Conclusion

With the problems laid out above, Jira Connector for SAP Solution Manager Focused Build can be a good fit if you are looking for a simple easy to set up and map Connector. It is a simple solution that provides you the end-to-end insight needed to make the decisions necessary from leadership as well as manage the daily work for development/testing.

Still, I have questions? Contact a member of the CoreALM team today and discuss your needs further. As an SAP Partner, we can help you from planning to deployment of the Jira Connector for SAP Solution Manager Focused Build, advise on the right mappings to set and provide training.

Setting up the Jira Connector is easy and can be done in minutes with dynamic mapping – a very flexible dynamic mapping of different issue types, status, and fields between SAP Solution Manager Focused Build and Jira supporting different use cases. If you are interested in seeing this in action, contact one of our experts here.

Found this useful?

Italian Trulli

Schedule a workshop with the industry experts.

What’s new in Solution Manager SPS13

Test Suite Updated  - The Comment field is now visible by default in the Test…

read more