Convert Issue reporting sample app to Work order management app
The Issue Reporting template Power App for Microsoft Teams is designed to be flexible and extendable, including for scenarios other than tracking issues.
For example, in a simple work scheduling scenario, you may want to use it as a work order management app. There are many similarities between issues and work order—assigned users, task descriptions, and due dates.
In this lesson, we'll walk through changing the app to a work order management app.
Watch this video to learn how to convert Issue reporting app to Work order management app:
Open the Power Apps app in Teams. We recommend you right-click on the icon for Power Apps in Teams, and pop out the app so you won’t lose your changes if you go somewhere else in Teams.

Select the Build tab.
Select the team in which the app is installed.
Select Installed apps tab.
Select Issue reporting in Issue reporting tile.

The app will open in the designer with the Landing Screen displayed.
Select the text label control under the image that says Issue Reporting and expand the formula bar.
Understanding localization
Before we continue, it's important to understand localization in canvas apps. All text labels in Issue reporting use localization variables to localize text language to eight different languages. If you overwrite this formula with static text, the app won't be localized for other languages.
To maintain localization, create a spreadsheet with these three columns:
- OOBTextID—this is the identifier for the text control.
- LocalizedText—this is the text to display.
- LanguageTag—this is the code for the language.
For example, in the current expression for the label on the Landing Screen sets the OOBTextID of the text label to lblLoadingText__locText. Since static data in the app isn't modifiable, we'll choose a new OOBTextID for the control so the original one will no longer be displayed.
The spreadsheet we would import would look like this:
| OOBTextID | LocalizedText | LanguageTag |
|---|---|---|
| lblLoadingText2__locText | Work Order Tracker | en-US |
Add another rows for each additional language that you'll use, and add rows for each additional control for which you'll be updating the text. Then import to the app. Update the following parts of the expression formula:

The app loading screen now displays Work Order Tracker
![]()
Update the other screens in the app
Let’s update the other references to Issue Reporting to change to Work order
Update Insights screen
Select Tree View from the left-pane.
Select Insights Screen.

Select the Report an issue button and select the Text property.
Following the steps in the previous section, add a row to the spreadsheet for a new OOBTextId with the LocalizedText Create a Work Order and update the button text formula to reference the new OOBTextId.
Select the Issues reported by you text label, and select the Text property.
Following the steps in the previous section, add a row to the spreadsheet for a new OOBTextId with the LocalizedText Work orders you created, and update the text expression to reference the new OOBTextId.
The Last 7 days area is a component that combines text and dynamic content for record counts. The text is set in the Items property. In the area highlighted in the below image there are two text strings, one for singular and the second for plural. Following the steps in the previous section, add a row in the spreadsheet with a new OOBTextIID with localized text, one for Work item and the other for Work items.

Update Issue Report screen
The issue report screen is the screen that users see when the create an item, such as an issue or a work order. We'll use the same method to update the field text as we did on the Insights screen.
Select the Tree view.
Select Issue Report Screen.
Update the following properties:
- Change Select an issue type Text property to Select a work order type.
- Change Submit Issue button Text property to Create work order.

Update Template Selection Screen
The template selection screen is what users use to select the type of issue. Since we're changing the purpose of the app to a work order tracker, we'll want to change the Back to issue link at the top of the screen to say Back to work order.
The header of this screen is a component as it is reused between multiple screens.
In Tree view select Template Selection Screen.
Select Back to issue.
Select the InputHeaderText property.
Change text to Back to work order.
Update Assignment Selection Screen
The assignment selection screen is what users use to select the person to whom the item should be assigned.
In Tree view select Assignment Selection Screen.
Select Back to issue.
Select the InputHeaderText property.
Change text to Back to work order.
Update Issue Submission Screen
The issue submission screen is the screen that users see after an issue has been submitted. This has a text display control that displays a mixture of localized text and dynamic data for first name.
In Tree view select Issue Submission Screen.
Select the text label with the text Thanks, (first name). Your issue has been reported and should be resolved by”.
In the HtmlText property, find this section:

In your spreadsheet, define a new OOBTextId and set the text to
Thanks, {0}, your work order has been created.The 0 will be replaced with the first name of the user.
Update the highlighted part of the formula to reference your new OOBTextId.
Rename the Issue Reporting tab
We've now changed all of the references to “issue reporting” in the app, so now we want to change the name of the app so that users will see the correct name in Teams.
In Teams, go to the channel in which the app is installed.
Right-click on the app tab, and select Rename.
Change the name of the tab to Work order tracker.

Rename the app
We'll also want to change the name of the app so that users who select the app for general distribution from the Teams store can find it.
Open Issue Reporting in the Power Apps app in Teams.
In the upper right corner, select the app name.
Enter Work Order Tracker and select Save.
Next steps
To complete the scenario, consider making similar changes to the Manage Issues app so that the administrator experience also follows the same logic.