Let Business Teams Prioritize Their Own JSM Requests

[#1]

Your business teams already know what they want first. They just need a place to say it.

If your IT department receives business requests through a JSM portal, you probably have a prioritization meeting on the calendar.

And before every one of those meetings, something predictable happens.

Someone from the business side opens an Excel file, lists the requests they care about, adds a column for when they want them, and sends it by email. IT receives it, cross-references it with Jira, and prepares for the meeting. Then the meeting happens. Decisions are made. Someone updates Jira manually afterward.

This works. Teams do it every month, every quarter, every QBR. But it is more steps than it needs to be.

---

The root cause is simple. Business teams do not have Jira licenses. They cannot update the JSM portal directly to say what they want and when. So they say it in Excel. And IT translates.

The meeting itself is not the problem. Prioritization decisions benefit from a conversation. What costs time is everything around the meeting: collecting input, aligning versions, updating the system after.

---

With Advanced Portal Reports [Advanced Edition], business team leads can do this directly in the JSM portal.

They see the full list of their department's requests in one place. No Jira license needed. Seeing everything together is what makes the difference. They can compare requests against each other and decide what matters most relative to everything else, not in isolation. 

Then they set two fields:

• “Business Order” a sequence number that reflects their preferred order

• “Requested Time Period” a drop-down list with requested time period for when they expect delivery

Both fields are editable directly in the list view.

IT sees the updated list before the meeting starts. The conversation can focus on what actually needs a decision, not on gathering input that the business side already had.

After the meeting, there is nothing to translate. The fields are already in Jira. The changes are logged automatically.

---

Prioritization input is business knowledge. It lives with the people who understand the department's goals, deadlines, and trade-offs. The IT team's job is to receive that input clearly and act on it, not to extract it meeting by meeting.

When the business side has a place to say what they want directly, the meetings get shorter. And the list in Jira finally reflects what the business actually thinks, not what IT understood from an email.

---

Advanced Portal Reports for JSM is available on the Atlassian Marketplace. If you are already using it and want to discuss your setup, our Customer Success team is available.