Hi all,

Thank you so much for your votes and comments on this suggestion.

We are doing further research on this topic and would love to invite you to take part in an upcoming customer research study!

What’s involved in the research:

• Sessions are 1 hour and conducted over video-conference, so you can participate from anywhere around the globe.

• During the research, we'll start with a general chat to get to know you, then explore a prototype and complete some tasks.

• As a token of our appreciation, you'll receive an e-gift card worth $120 USD within 5 business days of completing your session.

Interested in taking part? Follow this link to fill in a few more details so we can make sure you’re a good fit.

If you have any other questions at all, feel free to reply to this message or email me directly on rpit@atlassian.com. We look forward to meeting you!

Cheers,

Ruvi Pitiyarachchi

Design | Jira Transformation

I don't understand why we're limited to one per project. In software we don't have this limitation, and neither does the old helpdesk. Once again, a basic functionality that is not included in an application that should allow it. 

My company often holds various business meetings about different projects that we are doing now, and to make it convenient for everyone, we book conference rooms with unspot. I have known about this system not so long ago, but the fact that it works perfectly and is more than functional is unequivocal.    

Now that we have to pay for JWM - I'm hoping some of these high value features get done.

Eric Zheng,

The use cases I have for this functionality are:

• Since work managment doesn't support Developer Tools, we use another project to manage our development tickets.  If Work Management supported Developer Tools (GIT repo connection), then maybe we could manage our development there per project.  But right now we need to link a work management ticket to a development ticket to indicate they are related...but we can't see it on the board or timeline.  I would prefer to link to a dev ticket because Work Management does NOT support custom poject templates, so having our development workflow in each work management effort would be difficult to maintain since it would have to be setup manually every time.
• We use another project in Jira to manage our day to day Requests/Incidents. It would be helpful to create a Request in another Jira project and show it as a child of a work management project task.  We have situations where we need work done by others that are not directly related to the project. This could be related to a standard/repeatable request with a system admin.  But they are not involved in the day to day of the project it will benefit.

Hi @Eric Zheng, 

I tried to book a slot but is completely different from my time-zone. Can we contact someone else to share some feedback on this?

Also, I tried to search but couldn't find anything on that so far - are you planning to have the availability to group per teams on JWM Board?

BR, 

Magdalena Zhisheva

Any plans on this?

Hi everyone,
My name is Eric - I'm a Product Manager working in the Jira Work Management team at Atlassian. Thanks everyone for voting and commenting your feedback below. I would love to learn more deeply about your use cases and understand the problems this feature request would solve for you.

If you’re interested in chatting to me about this, please grab a time on my calendar via this link: 30 Minute Meeting - Eric Zheng

Looking forward to speaking!
Eric

Please - we can't save Quick Filters to Work Management Board/List view that uses currentuser(), and we can't show sub-tasks unless the current view also includes the parent, which for our use is often not the same user. Let us create a board that is closer to what we can make in software!

This is a very important feature for us. It is hard to get buy in from business users when they are limited in how they organize their information.