is there a way we could assign an additional priotity type "Blocker" just on the internal Service Desk? Example: a customer may rate a problem "Critical", but we internally may then "upgrade" this to a "blocker". Customer shouldnt be able to choose "Blocker" in his customer portal, though
Similar to Workflow status, where we can rename the status , so if is different on portal but internally it is different
Maybe there is a misunderstanding of my requirement.
My expected setting is,
1. Customer sees only 3 Priority values (low , med , high)
2. But internal team can upgrade the Priority high to blocker. so internally it is seen as blocker and for customer it is shown as high.
3. Ideally you have 4 priorities , but only 3 are visible in customer portal
Is this possible ?
Dear @DeepakMurugesan if you are from development backroad then i would prefer to work on script runner, here you go for details,.https://scriptrunner.adaptavist.com/5.5.8/jira/quickstart.html
or there is one more option if you like.
Create priority field with 3 Priority values (low , med , high) which will be on customer portal.
Create another filed with Priority 1 or what name you would prefer. with value critical
and add it on edit screen. so that support can select critical if they want to change.
for temporary you can go with this solution.
or else if you can understand script runner that you can get what you are looking for easily,.
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events