We are working with several projects and I am trying to create queues to segment only valid tickets from each related project.
to understand it better, I run our Support channel and get tickets into a SUPPORT project and in case needed, I link my tickets to related PROD and/or RND projects.
I am trying with no luck so far to create simple filters with all tasks in SUPPORT that have linked PROD tasks, and similarly all of those with RND tasks.
My first impression was that having a field called issueLink will allow me to apply that with advanced syntax options, but that doesn't seem to be the case.
Even trying to set issueLink is not EMPTY appears to be a valid syntax but produces no results suggesting this field requires an actual task ID and doesn't fit my desire.
Thank you in advance,
Daniel
Very interesting requirement!
AFAIK, there is native JQL function which can pull linked issues from a specific project. There may be some 3rd party add-ons which can provide this for you.
I am curious to know how you are creating the issue in PROD and/or RND projects and link them to SUPPORT project.
I would propose to create a new single select list customer field (lets call it Linked Ticket Project) with options PROD and RND it it. Add the new field to SUPPORT project view/edit screen.
While linking the issues between SUPPORT and PROD/RND, set the value for Linked Ticket Project.
Then you can write a simple JQL based on Linked Ticket Project field value and use it in your queues.
Hello @Veera and thank you for the quick reply.
I am not sure I understand your suggested answer as I am already using a default field of Linked Issues on my current queue. maybe you can give me an example?
Check the link below for my simple example:
https://www.screencast.com/t/d8lccJ4mc23
right now since I couldn't create distinct queues as explained before, I simply make sure to have a list that displays all tickets combined.
to answer your question I use the Link or Create Linked Issue options from within the SUPPORT ticket (for either linking an existing ticket OR create a new linked ticket respectively).
https://www.screencast.com/t/ArhCGpnJ
I am now trying a different approach, going over all the relevant tasks and adding filterable items (thought about giving them distinct 'component' OR 'label').
I'll be able to apply filters with these new fields, but still I feel that being able to filter by the Linked Issue field could improved my queries and simplify things.
thanks again 👍
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The default Linked Issue / Links field just pulls the linked issue key. But, we can't apply filter for Project key using this field.
My suggestion was similar to your approach - i.e., adding filterable items (thought about giving them distinct 'component' OR 'label').
Instead of using 'component' OR 'label' fields, I was suggesting to use a new custom field of select list type. It doesn't matter which field you use as long as you will be able to use that field in the JQLs used by the queues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are welcome @Daniel Landman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.