Configuring Swim Lanes based on EPIC label but also displaying subtasks

[keith kennedy]

Hey All,

Hoping you can help me find a solution. My employer won't buy any plugins so I'm hoping for a clever way to get the view I need.

We recently switched from a Scrum board to a Kanban board, we are focusing on the batches of work that we bring across our boards rather than the individual subtasks that make them up (coding, testing etc). 

We are also using "Classes Of Service", namely "Expedite,  Fixed Date, Standard, Intangible". These labels are set an an Epic level, this was easy to display on our Kanban board through configured swim lanes as follows:

issueFunction in issuesInEpics("labels in (Expedite)") or labels in (Expedite)

ATM we only view Stories so the above works fine, but the team want to see the subtasks on the Kanban board directly, if we click on the ticket the subtasks are listed in the right pane but this isn't great for a stand up, the team would find it easier to see what status each individual subtask is in on the Kanban board, "In Development", "In Review" etc.

However, as soon as I change my board sub-filter to allow subtasktypes() in, my swim lanes disappear, I imagine because the subtasks are not directly associated with the labels as per the grandparent (EPIC). Is there any way I can inherit this label down so that it can make my swim lanes work again?

Thanks.

[Abdoulaye Kindy Diallo]

This is a Restricted Function in Atlassian OnDemand . As per policy:

Custom Domains — Your instance will be accessible at https://<account_name>.atlassian.net, where <account_name> is a unique word you specify when signing up. Use of custom domain names is not currently supported.

Changing Domains — Currently we're unable to change your Atlassian OnDemand domain after the instance has been created. Please choose carefully when signing up.

The workaround would be to have Atlassian sales (sales@atlassian.com) delete your current instance if you don't need the content and you sign up for a new one with a new <account_name> .

Hope that helps :)

[Manuel Heidler]

Well, I know this, but the suggested solution by deleting and signing up new is not what I'm looking for and what is not creating real value to customers.

Something to think about: Do you think we pay 8k € per year for something we don't need?
Don't get me wrong here, but I would never propose something like this to a customer who pays a lot of money every year for our product.

Can't we use something like an export and import feature?

[Jobin Kuruvilla [Adaptavist]]

You should raise a ticket with Atlassian support. I am sure they will be happy to help.