Create an JIRA issue from the mobile app I am developing? (iPhone and Android)

Dinghao_Zeng

Is there a way to share a text and image from my app I am developing to JIRA mobile app in order to create an JIRA issue.

The purpose is to allows our QA reports bugs directly from iPhone or Android while using my app, with pre-filled text and screenshot attached. 

Ideally I should be able to launch the JIRA mobile app from my app and attach the screenshot to it.

 

I checked the share panel but seems like JIRA doesn't develop a share extension.

Carlos Khatchikian

Hey Dinghao, I am Team Lead of Jira Mobile and I can give you some tips to accomplish what you want...

First of all, there is no easy way to pass parameters to create an issue in mobile. The most you can do is to pass an attachment and then create a ticket from there.

But you have other alternatives that could work really well for you..

Option 1: Use Jira Mobile Connect

Jira Mobile Connect is a plugin created long time ago. If you enable that in your Cloud instance in the project you want to use when they users use the library they will create tickets with the specific configuration that you asked for. The only limitation is that the reporter of the ticket will be the bot account the plugin creates.

You can see more information of Jira mobile connect here: https://bitbucket.org/atlassian/jiraconnect-android/src/default/

The good of this one is that it is easy to configure and you can append a lot of data in the description or custom fields. This way you can even get library versions, which flags are enabled, etc, etc. Basically you are going to send an API to Jira with all the things that you need. This is actually what our Mobile apps are using.

Options 2: User Jira Service Desk

You can also use service desk widget API to create tickets with email addresses. You would need to have a Service Desk license and you would have to be an agent.

More info here: https://confluence.atlassian.com/servicedeskcloud/get-requests-from-an-embeddable-widget-937890652.html

For small/medium teams I would go with Option 1. If this is a big team I might go with Option 2. 

Hope this helps!