You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi. I am trying to determine if Jira Work Management(JWM) will support our use case. We have a team of 40 non-developers that are trying to get off of MS Teams and Spreadsheets to manage "work" requests. We are currently using Jira/JSM premium for our software teams. We also have Access enable using OKTA for our org
I am trying to determine if JWM will work for this team so anyone in our org can "send" them work, but the internal team is the only group that has access to work the tickets, and close them. There is the "anonymous" feature, but we want to limit access to creating tickets to only people in our org (not public), and use the information in Access to record who the requester is. Thx
Not sure that I completely follow you, but I think we can get through a series of questions.
And yes, I think you will be able to us JWM for that.
1. Do the 40 people have Jira licenses already?
2. You can setup issue level security so that once a card is created, only certain people can see that card and make changes.
3. You want to capture the Jira user who made the request (the reporter).
Are we are on the right track?
We are trying to determine which product to use, so it is a bit vague.
Do you want anonymous access? I am confused about that.
And yes, it sounds like JWM is the right fit, especially if all of them already have Jira licenses.
This group of 40 currently doesn't have Jira Software licenses. They are in Access today for the purposes of creating Service Management tickets.
This would be a new product add for us for non-software development teams.
The reporters creating tickets would be employee's of our company, but not members of the team/group that works is being requested of. They would not necessary have product access.
One other requirement is that the reporters can upload documents to the team (usually spreadsheets).
Gotcha - all of that works with JWM.
First, the 40 would need regular Jira licenses.
Second, yes, the current employees would be able to create tickets for the project, but would be prevented from seeing the tickets once created.
Third, only a Jira administrator can upload spreadsheets (CSVs) into Jira (which creates tickets). But that's a Jira rule across the board, not just for JWM.
The good thing about JWM vs. JSM is that the users would not need the extra Agent licenses in order to work with the tickets.
Thank you for all of the answers. A couple of more questions:
Thanks again for all of your help.
Thank you @John Funk for helping out with Ken's questions!
@Ken Young , I'm one of the Product Managers working for the Jira Work Management team. I'm sure you've found John's answers helpful!
If you're interested, I'd love to be able to run you through a quick demo of the product, and perhaps walk through some of your requirements and how JWM might be able to help you with what you need.
Feel free to contact me directly via email: email@example.com and we can set some time up to go through any more questions you might have about JWM.
Thanks for the input @Jane Yeoh ! And Ken you should definitely take her up on that offer. :-)
But a few more answers.
1. The users will only need Jira Core licenses. If you already have Jira software, those would be the level you need. And you can't carry a combination of some being premium and some not. So, all of that being said, you will just need to get more licenses of what you already have - whether it is premium or not. But you don't need Premium if you don't already have it.
2. So it just sounds like you would be uploading an attachment to an existing issue. That works fine.
3. Yes, you can link JSM and JWM. We do that through Automation rules.