Raise it for a colleague.
Let Jira Service Management customers raise a portal request on behalf of a colleague in their organization, the way agents already can.
Free for up to 10 agents · Jira Service Management · Runs on Atlassian
A Jira Service Management app that adds “Raise this for a colleague” to your customer portal. The colleague becomes the reporter and gets the emails, the person who raised it stays on the request, and customers can only pick colleagues who share one of their organizations. It runs entirely on Atlassian, so no data leaves your site.
Raise it for a colleague
On the portal form, customers see “Raise this for a colleague”. They type a name, pick the colleague and send the request as usual. Left empty, the request is theirs, exactly as before.
- Works on every request type, forms included
- Names only, never email addresses
- Customers in no organization see nothing new
Both stay on the request
The colleague becomes the reporter and gets Jira’s usual emails. The person who raised it is added as a participant first, so they never lose the request and see every update.
- The colleague is the reporter, as if they raised it
- The person who raised it stays as a participant
- A note on the request says who raised it for whom
Colleagues only, never the customer list
Customers can only pick colleagues who share one of their organizations, and only organizations added to the service project. The server checks the choice again before anything changes.
- Limited to shared organizations
- A changed form is refused on the server
- Agents keep Jira’s own field; On Behalf is for customers
Admins stay in control
Turn it on or off, choose the organizations that can use it, switch it off for chosen service projects and see every request raised for a colleague in the last 90 days.
- Allowed organizations and excluded projects
- A public comment so the colleague is told, or not
- 90 days of activity with the result of each request
A look at the real screens
The real app on the Jira Service Management portal, with sample requests. Open any screen to see it full size and zoom in.
The portal form with the colleague picker under the usual fields.
1 / 3 · On the portal
Everything On Behalf does
One app for every service project on your Jira Service Management site.
Raise for a colleague
Customers raise a portal request for a colleague, the way agents already can.
The colleague is the reporter
They get Jira’s usual emails and see the request as their own.
The raiser stays on it
Added as a participant before the change, so nobody loses the request.
Shared organizations only
Colleagues come only from organizations the customer and the service project share.
Checked on the server
Every choice is checked again before the reporter changes. A changed form is refused.
Names only
The picker never shows email addresses or the full customer list.
A note on the request
A public comment and a note on the request page say who raised it for whom.
Forms included
Works on request types that use Jira Service Management forms.
Admin settings
Allowed organizations, excluded service projects, the comment and the language.
English, French and Arabic
The portal and the admin page in three languages, Arabic right to left.
Runs on Atlassian
Built on Atlassian Forge: no data leaves your site and nothing is stored outside Atlassian.
Zero setup
Install it and the option appears for customers who belong to an organization.
Pricing
Per agent per month, billed through the Atlassian Marketplace on your site’s Jira Service Management agent tier. Every plan starts with a 30-day free trial.
1–10 agents
Free
11–100 agents
$0.75
per agent per month
101–250 agents
$0.55
per agent per month
251–1,000 agents
$0.30
per agent per month
1,001–5,000 agents
$0.12
per agent per month
5,000+ agents
$0.06
per agent per month
Questions, answered.
Anything else? Contact support
- Not on its own: only agents can. On Behalf adds it to the customer portal. The customer picks a colleague from their organization, the colleague becomes the reporter, and the customer stays on the request.
- Only colleagues who share one of their organizations, and only organizations added to the service project. An admin can narrow it to chosen organizations. Every choice is checked again on the server, so a changed form is refused.
- Yes. The colleague becomes the reporter and gets Jira’s usual emails. The person who raised it is added as a participant, so both see every update.
- No. The picker shows names only, and only for colleagues in a shared organization. The full customer list is never exposed.
- No. It is built on Atlassian Forge and runs entirely on Atlassian. It keeps 90 days of activity on your site and sends nothing to Systematic or anyone else.
- It is free for sites with up to 10 agents. Larger sites pay per agent per month through the Atlassian Marketplace, from $0.75 down to $0.06 per agent as the site grows, with a 30-day free trial.