Your top questions about the Jira Cloud for Mac app

[Irene]

Thanks for your patience as we’ve been carefully reviewing responses to our recent announcement. As a follow-up, I have consolidated top questions to clarify in this post.

But before diving in, I want to thank you all for your engagement with us. We will continue to listen to your feedback, and will answer any questions you have here in our community.

Doesn't Mac app share the same codebase with the iOS app? Tell me more about the effort required to maintain and grow this desktop app.

Yes, the Jira for Mac and our iOS App share the same codebase. However, there are some intentional differences between the Mac app and the iOS app in terms of design approach and user interactions that make it non-low effort for the team to maintain and provide the desktop experience that people want and expect from Atlassian.

When we first launched the Mac app, customers just wanted to be able to use the app for quick in and out tasks. Since then, we’ve spoken to many customers and heard that you all want more features in the Mac app so you can use it as an alternative to using the web version of Jira.

To add to this, we need to acknowledge that the vast majority of users of this codebase are iPhone users. Improvements that are the next most important things for our desktop users most likely are not the things that make sense for phones. As the needs of Mac and iPhone users widened, it made it more challenging for us to meet the needs of Mac users. We believe that the best desktop experience for Jira isn't going to be a Catalyst-ported iOS app.

Please add what you love about the Mac app here so we can better evaluate an alternate multi-platform desktop app.

I still want to use the Jira for Mac app! Can I?

Yes! You and your team still have access to, and can use the Jira for Mac app for the foreseeable future. We just won’t be shipping updates, bug fixes, or responding to support tickets starting in February.

Why are you sunsetting the Jira for Mac app when web performance is slower?

We hear your concerns regarding the speed of web, and are actively working on building the fastest version of Jira. In the last year we’ve made progress on several performance improvements, including making viewing issues 1.5x faster, and having issues create and loading dashboards at 2x faster speed.

We have work underway, are taking your feedback, and will continue to share updates in the Community.

I love Jira for Mac dark mode, will you bring it to Jira web?

We love that you love dark mode, and we are actively working on bringing this to Jira web. You can follow our progress at https://jira.atlassian.com/browse/JRACLOUD-63150.

Are you still investing in Jira on iPad?

Yes, we will continue support for Jira on iPad. In fact this decision will allow us to accelerate adding more tailored experiences and features for work on both mobile devices and tablets.

Thanks for your feedback

I appreciate you sharing your responses and feedback, and hope this post helped clarify some concerns. Please continue to share your experience, and we are here to help you navigate through the changes.

[C Abone]

This can be achieved using the 'Create issue link' post function and would only work as long as the issue is created within the Epic or linked to the related Epic using the ‘Epic Link’ field during creation.

In my case, i wanted any new story issue type to be automatically linked to the Epic using the 'blocks' option from the 'Issue Linking field during creation.

In the 'Create' transition, select the post function (Create issue link)

From the Issue s to be linked parameter, select the 'Field containing issue keys' option and in the dropdown,  Keys of linked issues

image2015-6-4 12:57:44.png

From the Issue link type to be created, I selected the 'blocks' option. You can select any option depending on the linking that is required.

image2015-6-4 12:58:12.png

Click on the Add button.

Don't forget to select the 'Publish Draft' button to save your changes

image2015-6-4 12:58:49.png

Hope this helps.

[Nic Brough -Adaptavist-]

Three things.

1. You need to think this through - how does a "user create a test case from a user story"? You need Jira to understand when they are doing this, which implies a workflow process or new option to do it as an action (like "edit", "comment" etc). Either way, you can then tag code into that process to do the linking

2. You can't install the plugins/code you might need to do this in OnDemand (and you'll probably have to write it yourself)

3. Have you looked at "subtasks"? Those are automatically linked to their parent.

[Thomas Varghese]

Thank you Nic for your quick response.

Since we are using OnDemand, I believe we can't create an "Create Test Case" action button like "edit" and "commit". But you have mentioned that cab write this code myself. Is there any sample code available for similar functionality available where I can use it as a reference

[Thomas Varghese]

Also for a typical software development environment, is Test Case is created as a Sub Task of User Stroy? Is that the best practice recommended by JIRA?

[Nic Brough -Adaptavist-]

You're missing the point in answer 2 - you can't install plugins or code on OnDemand.

Some people create test cases as sub-tasks under an item, I find it quite a clear and logical way to work. Others don't. It's more up to your processes and way of working - I can't give you a clear cut "yes, it's the best way to do it" here.

[Jobin Kuruvilla [Adaptavist]]

There are plugins that can do it but it is not possible on onDemand instance.