Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,252
Community Members
 
Community Events
176
Community Groups

JSM project design and API assistance

Edited

Hello everyone, I manage quite a large Jira instance so when I was handed a JSM instance for our HR team I thought. No problem this cannot be difficult.

 

Due to the way the team and the 'group of companies' operate it has been a little tricky because the team have demanded only one portal and many projects where the respective companies can work on issues.

How would you triage issues, if you would at all?

I do have scriptrunner available and I am quite comfortable  in Jira. JSM not so much.

Any references beyond the basics would be appreciated.

 

Happy Monday,

Graham

3 answers

1 accepted

1 vote
Answer accepted

For the same case I use Automation for Jira and Create Issue Event.

In Automation for Jira rule I check values of request fields and decide to what project to triage. After creating developer's project issue I link it to original issue with type Relates.

When developer's ticket is resolved it triggers another rule that finds original issue and makes a comment or resolves it as well depending on request type.

Another approach is to let developers work on portal requests directly. In this case you check fields value and assign this or that developer based on request.  The bad thing is that you will need to buy extra JSM license for each developer that can be assigned to request.

 

@Sergei Gridnevskii,

There will be around 20 projects and these will all be business projects where there may be many interactions between the reporter and the assignee but the Group team want to also track things like status in their own portal project.

 

I am using Automation.

This is really a call to sanitize my thinking with the assistance of the community. Thanks for your comment.

0 votes
Ajay _view26_ Community Leader Sep 26, 2022

Hi @Graham Twine 

JSM provides REST APIs... you may refer it here - https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/

To set up portal access you can refer to the product documentation - 

https://support.atlassian.com/jira-service-management-cloud/docs/set-up-portal-access-in-team-managed-projects/

For triaging Requests coming in via the Portal refer - https://support.atlassian.com/jira-service-management-cloud/docs/triage-customer-requests-for-your-agents-with-queues/

 

Since the use-case is not very clear could you please elaborate it further?

 

Cheers

Ajay

@Ajay _view26_I have my own DC cluster. All of your APIs are related to cloud

Hello @Graham Twine 

Yes You can create customer Portal, from where external customer can create the tickets to your jira instance. The Agents (JSM License Users) and collaborates (team member like Users) can work on those tickets. 

You can allow the customer to create ticket via portal or email. Check the setting in the customer permission navigation.

If you have any specific question please let us know.

Thanks

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events