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,762
Community Members
 
Community Events
176
Community Groups

Queues based on status of linked issue

Edited

We have been using Scriptrunner on Jira Server for that functionality in queues. Based on fields in the Service Desk and Status of a linked ticket, i can display tickets. For example a ticket in  the servicedesk is Chargable and linked to the "Chargable Tickets" project. Once it is linked there it is in queue Chargable in progress.. once it is done in the chargable tickets section it is moving to queeue chargable but completed.

 

The enhanced search allows me to setup filter with script runner but I cant use the function in the queues. Example so far

First queue - open work

status in ("In progress") AND NOT issueFunction in linkedIssuesOf("project = ChargableTickets and status in ('closed') ") Order BY updated DESC, priority DESC

Second queue - Completed work

status in ("In progress") AND issueFunction in linkedIssuesOf("project = ChargableTickets and status in ('closed') ") Order BY updated DESC, priority DESC

 

Any solution to this problem? Script runner just buffers all the tickets in a project and based on this, it searches every single ticket with that function. I can rebuild that with 1000 presumed Ticket Numbers but clearly that is not how I want that software to work.

In addition, I used the same function in conditions for workflows. You cant close a ticket when it is chargable and there is not ticket in "ChargableTickets" section

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events