for testers – fioritracker.org

Clarity on responsibility for SAP Fiori applicaitons

One of the major goals of project management is the clarity on responsibility. Fiori Tracker makes it crystal clear who is responsible for each SAP Fiori application made available through SAP Fiori Launchpad. The information is available in seconds directly from the application itself (with Fiori Launchpad plugin) or through the application card view. All applications in scope can be found with a Google-like search function. The responsibility is determined based on the application stream assignment: Each application is assigned to the stream and each stream has named functional consultant assigned. Applications that belong to P2P stream have P2P functional consultant set as responsible and so on, depending on how you decide to set up your streams. This way in case of changes in functional consultant position the assignment is passed through the stream assignment and there is no need to update and attributes of the applications itself. Same assignment rule is applied for Fiori Launchpad business catalogs, groups, and roles.

During the implementation phase, you will find this function useful whenever you will need to:

Set the scope for implementation, testing or for go-live readiness for each stream
Assign resolving issues resulting from testing the application
Make decisions on assignment to roles, Fiori launchpad business catalogs or groups

During support when:

Set the assignee for issues reported by end users

Use case: Finding out the test users for specific business roles

Each SAP S/4 HANA implementation project team member or support team member conducts the tests. On a daily basis, each specialist runs numerous test cases. Whenever it is testing during official test phases or replicating the issue that the end user encountered, there is a need to access the system with the user that has the respective business roles. As Fiori Tracker holds the repository of all business roles it is also the best place to keep the link of the roles to the test users.

This simple view that is available in 2 clicks saves a lot of time as SAP team members get the correct uses in seconds.

How to speed up Jira issue creation for SAP Fiori applications

There are two main phases in SAP systems life cycle when gathering feedback on how SAP Fiori applications are performing is important: implementation and support. In both cases, quick and accurate problem reports save the time spent on issue solving. This is especially the case for SAP Fiori applications where nontechnical users or even implementation […]

To address that issue we have prepared the plugin for SAP Fiori Lauchpad that enables users to report problems directly from the application that is having problems. The plugin is a part of Fiori Tracker tool and uses the information collected in its tables to automatically identify the running SAP Fiori application and populate the contents of the Jira ticket with relevant technical information.

With the press of one button user is presented with prefilled issue title with the precise name of the SAP Fiori application together with its technical id. In the description field, the user is only required to provide the nature of the problem that he or she encountered.

In addition, the plugin automatically collects the screenshot and allows the user to decide whether to automatically include it in the created Jira issue.

With Fiori Tracker and “Reporting issue” function your team will love the ease of recording Jira tickets while testing!

SAP Fiori – Atlassian Jira integration: Creating a support message

Imagine loving the ease of recording Jira tickets while testing! Report your issues with SAP Fiori apps directly form Fiori Launchpad or an application itself. SAP Fiori applications are identified fully not only with URL but with full friendly name and description. All relevant data like SAP system id, application name and application library id […]