Submit multiple tickets to JIRA from Asana integration

English Forum Product Feedback
,
1

Our projects are managed out of Asana and when it comes to tech support, we submit JIRA tickets.
I like the Asana - JIRA integration.
Sometimes, due to some processes we have I would like to link several tickets from JIRA to the asana task.
One JIRA ticket could be for the development part and another JIRA ticket could be for further support / amendments.

It would be great to have visibility on both within asana and give stakeholders the ability to submit 2 tickets for JIRA from within the asana task.

Thoughts?

1 Like
2

@ambforumleader can you please give this feedback some TLC.
Thank you all!!
Rashad

1 Like
3

A workaround might be to use two project layers.

The front project has all of the tickets, and has a rule that multi-homes all tickets that get the “jira-ticket” label to project two.

The back protect has the Jira synchronisation. It also should multi-home new tickets to the front project.

Create two kinds of tasks templates, one with the syncrhonisation label that should trigger the rule, and one without.

Now when you want to group two tickets, create a new task without the synchronisation that will house the tickets, and convert the two tickets into sub-tasks of the tickets.

Front project will have task + two tickets as subtasks.
Back project and Jira will have just the two tickets.

Does that solve your problem?

4

Or perhaps the other way around is more logical, use a custom field value that prevents syncrhonisation of the mother task. Then you could do with one task template that contains that label, that you only use for tasks that will house other tasks.

5

Hey @Jan-Rienk

Thanks for providing the workaround suggestions.

I feel that in order to implement that, my workflow could become complicted. Currently if a task is multi homed in two projects, and both projects have Jira integration, you will still only get one jira ticket. Unless I miss understood the suggestion.

Currently, I manage the entire incident management workflow on asana. The outcome is reportable to non-asana users. That is why being able to report on a single parent task, which will have two jira tickets (usually, one for IT internal support and one for external developer) would be ideal.

6

@Rashad_Issa Here, this is what I had in mind.

image
image1078Ă—692 46.1 KB

Two ways to get to this:
Either:

  • Create motherticket first (make sure it doesn’t get synced to back project and therefore Jira)
  • Create subtasks
  • Add subtasks to back project ([tab]+[p])

Or:

  • Ticket A and B are made first (sync to back project)
  • Make motherticket (don’t sync)
  • Convert tasks into subtasks of motherticket.
  • (optional) remove subtasks from front project

Handle automatic syncing by making a ticket and a motherticket task template that have sync to jira field set right for the rules you have in your front project.

You won’t use the back project. It’s just for syncing with Jira.

Does that help?

1 Like
7

Thanks @Jan-Rienk I will test and see if that works.

1 Like
8

@Rashad_Issa Have you tried Unito? It’s designed for exactly this purpose. Here’s a guide for syncing Asana tasks to Jira issues bidirectionally.

1 Like
9

Thank you @JoshG I will check it out.

1 Like