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
I am evaluating JWM for our non-tech usage. I plan to use it for our HR team to take action on tickets/requests and also our IT support team. I know that Jira Service Management is another solution, but I like that JWM is more flexible
As I understand it, the forms feature is only available for JWM users. Furthermore forms can only be shared or embedded via Confluence.
On the other hand, I found out that there is a Jira Power up in Trello for cards to sync to projects in JWM.
I checked on Zapier and found that the integration doesn't work with JWM but only Jira software.
Does anyone else have any other ways to create tickets in JWM boards or any integrations?
Hey @Soo Beng Ang ,
I feel like you are trying to over engineer your solution.
If you have requests coming in from end users then using JSM is the best product for that. If they then need to be handled in a JWM project (which could work) you could always use an automation rule to just "throw" the issue from the JSM project to the JWM project and sync both.
This way your customers/end-users will have a nice request portal where they can follow up and you can really manage your incoming requests properly while still maintaining the follow up and handling of the tasks with a related issue in a JWM project
Hi, @Dirk Ronsmans
is there actually a good way to do this?
When you say "throw", what kind of automation are you thinking of?
I see that in Cloud there is not automation available to Move the issue to another project, so what I saw suggested was to clone and delete the original request.
But Cloning the issue loses the attachments, and I believe the users no longer see them in their own portal requests.
If you have any helpful inputs, I would appreciate it.
I would indeed go for a Clone/Create a new linked issue in the JWM project (and also keep the original which would be customer facing)
Moving an issue would destroy so much of what was entered.
You would then have a Customer issue (JSM project) and a JWM issue that your other department can work on. (also going by the idea that a customer doesn't need to know your inner workings)
You could then sync back (comment and status wise) information from your JWM issue to your JSM issue to update the customer.
I think it requires a mental shift as to what team is working on what.
If you use JSM just as a portal to have the customer register the issue and keep them updated but have the "Agent" work in a JWM project then it works.
If you require more feedback to the customer then the Agent should also work in the JSM project (but they could still plan their work in a JWM project)
The 2 products are created for other uses so it really depends on what you want to do.
My suggestion is always, start with a small feature set and build out as needed. Don't assume your agent or customer wants/needs something that might be a blocked. Give them a basic implementation and have them give feedback on how they want/need to work and build on that.
Hi @Soo Beng Ang ,
As an option to collect feedback from employees or/and external customers directly to JWM projects, you can use Customer Case for Jira app.
You can create forums for your existing Jira projects other than JSM. All the tickets created in the forums will be automatically visible on the relevant Jira project and vice versa. A forum can be public (visible to everybody), private (restricted for specific email addresses or domains, for example, for your internal needs), or you can set it up as a support service just as JSM(private communication with a support assistant).
Hi @Soo Beng Ang ,
If you are using JWM, users with license can only create ticket, work on tickets. This will cost you.
If you use JSM, then you can have a customer portal and user can create requests from customer portal and team can work from backend Jira. You would require only license for the teams who work on tickets.
Example: If you have 100 people and out of which 10 are from HR, to use the JSM you need only 10 user license.
But to use JWM, you need 100 license if all users needs access to create tickets.