Today, I have an interesting and fun Table Grid Next Generation (TGNG) use case for you: burger shop order management.
Imagine you’re running a burger shop. You’ve got an external data source that stores your menu. This shop uses Jira Asset to manage its menu and uses the customer portal to receive orders from customers. Each order becomes an issue in Jira, giving you a full picture of what your customers want, all in one place.
Note: In order to use the data from an external data source, you will have to use an external database system such as MySQL, Postgres, SQL Server, etc.
In this example, we will use REST as our external database system.
Here’s a rundown of how it was set up.
1. Logged in to Jira? ✅
2. Installed Table Grid Next Generation? ✅
3. Premium Jira Service Management plan to use Jira Assets? ✅
You’ll also need a related Jira project and issues set up, plus an admin role for access.
Here’s how the use case looks visually.
1. Open Jira Assets and create a new schema called "Burger Menu."
2. Set up an object type called “Dishes”.
3. Add attributes like Price (use "Float" for the type to handle decimal prices).
4. Start filling in dish details!
Now, you’ve got a menu right inside Jira. 🎉
Since our burger menu data lives outside of Jira, we’ll use REST as our bridge. Here’s how:
1. Go to Data Sources and add "Burger Menu" as the name.
2. Choose Datasource Type = REST and fill in your REST API details
3. Fill in your Basic authorization details. Ensure you choose the POST method.
4. Test the connection, save, and voilà—Jira is now linked to your menu data.
Now that the menu’s ready, create a Request Type called Order Burger for customers. This way, when they select “Order Burger” on the Customer Portal, it’ll open a form where they can pick menu items directly from Jira Assets.
Now for the fun part—setting up the Order Burger grid in Jira.
Here’s how:
1. Add Grid Columns like “No.”, “Name”, “Price”, and “Total.”
2. In Scopes, select your Projects, Issues Types, and Service Desk Request Types on which you want to display the grid.
3. Link columns to the burger menu data and create formulas to calculate prices dynamically. For example:
- A simple formula in the “Total” column calculates: `Price x Amount = Total`.
4. Save the configuration, and your grid is ready for action!
Finally, hop over to the Customer Portal, select Order Burger, and add rows to your grid as customers add items to their orders. The grid will show up on the issue view, giving you an instant snapshot of every order, plus a total cost calculation.
This setup was so much fun to create, and I love how it makes menu and order management so much smoother. You can find the whole use case here.
If you’re thinking of doing something similar or want tips on adding formulas to the grid, give me a shout!
Hope this helps someone out there get creative with TGNG! 🍔
francis
Atlassian expert
Exalate
Belgium
42 accepted answers
1 comment