Mobile working with JPD (Android, iOS)

[Jan-Hendrik Spieth]

The Jira mobile apps for Android and iOS can already display JPD-Issues/Ideas quite ok-ish, but some things are still missing.

In particular, the Delivery and Insights tabs aren't available.

And of course, there are no "mobile" Views (lists, boards, charts), yet.

I can't say yet if and how I would want to work mobile with JPD. Adding insights would probably one of my typical tasks, though.

Out of curiosity: What plans/ideas/visions does the Atlassian team have for mobile working with JPD?

[Pieter Helsen]

Hi,

My approach is a little different. Instead of automating the creation of the Delivery Ticket/Epic, I automate the status transition upon creation of a Delivery Ticket (along with some other tasks such as creating documentation in Confluence and creating some placeholder tickets under the delivery ticket).

The reason why: typically the title of my ideas is long and I typically summarize the Delivery Ticket name so that Epic badge in the engineering backlog is easily readable. 

For example:

• Idea summary: Research what our customers want from a dashboard
• Epic summary: dashboard research

[Ka Silveira]

@Furkan Akduman I create this automation:

and it works perfectly!

I change my Idea status so a new epic is created and linked to my Idea:

It's no necessary to pay a license for automation user! Please verify if your automation is configured by your two projects (Jira and JPD). Check if you are using the correct link (implements if you are editing epic, "is implemented by" if you are editing the Idea.

[Furkan Akduman]

Thank you so much for your help 🙏🏼 I have understood the problem as i described below: I encountered an error due to the absence of the linked Issue field on creation screen. 

[Ka Silveira]

Hey @Furkan Akduman the problem can be the link you used to vinculate your Epic and you Idea. The link used on JPD is a new "Polaris issue link" (Implemented by -> Implements). Take a look on this!

[Karin van Driel]

Hi @Ka Silveira 

Somewhat off topic, but thank you for adding a new word to my vocabulary, had not heard the word 'vinculate' before! :) 

[Nick Haller]

Hi @Furkan Akduman ,

You should be able to find a similar preexisting automation template under each of your JPD projects' Automations tab for this exact use case.

You'll just want to select which Jira project the delivery is created under, as well the issue type (such as an Epic):

[Furkan Akduman]

I have got an error (attached), do you have any idea about this, I have used the default fields come from the template but messages highlight field ignored (Linked Issues). 

[Nick Haller]

I would switch the Actor of the automation to yourself (or someone that can create the Epic), then retest.

If that is successful, then it's most likely an issue with the A4J (automation for Jira) user, and them not having JPD permission. You'll have to open a ticket with the JPD support team to enable this user / permission: https://support.atlassian.com/contact/

[Furkan Akduman]

Finalllyyy 🥳, I have solved the problem, here is the solution, the thing is not related with an actor,

• The linked issue field is not included on the create screen

I have edited the Epic creation screen & add to linked issue field, the automation is working now