AFA (Ask For Anything) – Jira Work Management

[Chase Wilson]

Calling all Community members!

You want it, we want to hear it – Jira Work Management edition.

Whether you're a Jira Work Management pro or a complete newbie, check out our product and let us know your laundry list of wishes, feedback, and recommendations. No request is off-limits so long as it's polite, constructive, and appropriate. Bonus points for those who represent the things that your non-technical teams want or need. 

We will do our very best not to mention the word "Backlog" ;)

The founding team of Jira Work Management will be here to ask for any clarifying questions or to let y'all know if we're already building it! You may see some guest stars from the rest of our team as well.

We'll choose one commenter randomly and send them a very special JWM package. Vague on the benefit here but mostly this is a chance to give thoughts about JWM. As many of our Community Leaders here can attest, we really do try to implement your thoughts and feedback if our team is able to.

Oh, best of all.... JWM is free for any instance with any Jira Cloud product. Simply make a business project and you'll be off to the races. Enjoy!

How-to guide

1. Write down all your wishes and feedback in a comment
2. Give your feedback bullets a 1-5 rating (1 = Could be nice, 5 = Won't use JWM without it)
3. Let us know in your comment if you're open to us contacting you directly about your feedback
4. *Bonus* Help us prioritize better by explaining why your organization wants or needs what you're asking for

Resources

How to make a business project

Product homepage

The Founders

Marketing - @Chase Wilson 
Product - @Ron Levy 
Design - @roto 
Engineering - @jtblin ︎ 

Disclaimers

This is a test run for a new way to get feedback. Candid feedback is  , unnecessarily mean / rude feedback is . We're real humans!

Cheers :) 

- The JWM team

[Lucinda Pagett]

Hi @Chase Wilson

Scale- 4 (this would be an absolute life saver to have)

We are just trialling your Work Management program for our Marketing/ Innovation team and there is just one problem we have (but it isn't an issue on Jira Software).

We would like to sort our projects based on Epic, and then have the associated tasks appear below the Epic (as seen on the right hand side of the below screenshot).

I noticed that it already does that for the task with sub tasks but those tasks are within one of the epics (but don't appear like that on the timeline, list or board).

Is there a way we can change this in the settings so that it appears more like the image on the right? We want the functions of Jira Work Management but need the layout of Software to organise our marketing projects.

Also as a note, when I created issues within the epic, they don't appear under the epic when I open it (as seen on the right again) - is this also something that can be changed in the settings?

Thanks,

Lucinda

[Kathy Woolverton]

Scale = 5

Definitely need the ability to automatically sort the display in all areas (for example: in Lists, Timelines, Calendar, and Issues, etc) by the full hierarchy.

However, every new Task created under an Epic shows up at the very bottom of the list of all project issues. Then users think there was an error saving. 

The current manual work-around is the user has to go to List view and manually drag it up to the correct epic, which is especially problematic for big lists. Users shouldn't have to do this sort manually, when it should be a very quick fix to add a hierarchy sort.

With this hierarchy sort, adding the ability to expand and collapse the view would be very useful, like the > which currently only works between tasks > subtasks.

This hierarchy sort should be as defined in Issue Type Scheme - see screen shot below), rather than hard coded. 
For example, in our current business project, we are using Epic > Tasks > Sub-tasks.

[Jackie Sutter]

I agree having tasks within the epic under the epic (like in the traditional JSM view would be very helpful)

[Vicky Gibson]

Another Hands up for this Also! Please add this as the Kanban board gets a little confusing with out the proper structure. 

[Darius]

Temporal guest access for external collaborators please. 

Rating 5

Im looking at the viability of migrating from ASANA Business to JWM Premium. It is unfortunately a non-starter because of this missing feature. 

[Dave Liao]

Multiple Forms for a single project, please!

Score = 2

And maybe a way to copy/clone a Form to make it easier to make variants of a base Form?

[Chase Wilson]

You and @John Funk both! We're definitely looking into this already. Current solution idea is to have one form per issue type, per project. Would that be a good enough solution or were you looking to have multiple forms per issue type?

Copying a form is interesting – is this across projects or in the same project?

[Dave Liao]

Within the same project ☺️

[Markus]

@Chase WilsonI dont want to get too ahead, but i know you guys purchased the company behind Proforma. Pretty much everything in that app in terms of forms is fantastic. As close as you can get to integrating those features i think would be pretty cool! Proforma comes with a copying feature.

[Chase Wilson]

Shucks, meant to compliment you on the GIF in my last message but forgot  . 

So, to both of you for Proforma, how do you feel about the fact that Proforma more-or-less attaches records of the form submission to an issue? We've been going back and forth about Proforma since the mental model works quite differently. We can add a lot of Proforma functionality to our existing forms, or adapt Proforma and lose a few current features that we like.

It's something we're looking into a lot right now (there's an active decision being made) so would you two be open to us reaching out to ask clarifying questions about your use cases? Cheers!

[Dave Liao]

@Chase Wilson - I'm always up for a quick chat, especially in reference to Proforma's model of attaching records to issues. I'd ping Markus first, as I haven't used Proforma in a bit. 😁

[Chase Wilson]

@roto let's set up some time to chat with Markus (and Dave as well just to catch back up with him). As an FYI, we should have some decisions made on this front very shortly that we can communicate with you offline. Cheers!

[Markus]

1. Multiple forms and linking to other projects - 2
   • I assume this will come in the future with the proforma purchase
   • The ability to link a form request to another project through a search bar would help my team stay more connected and less siloed
2. JQL / Filters are highly needed for the board view to help my team look at and sort the data - 4
3. Different views on the Timeline - 3
   • Displaying assignees on the left and tasks on the right for a resource view would be AMAZING. Would help my team plan our projects and see where our resources are allocated

[michael.helms]

+1

I'd also like the option to see subtasks on the calendar and timeline view.

[Chase Wilson]

Thanks for the feedback @Markus !

1. Noted, sounds like a common request on this thread. Definitely something we're already evaluating the effort of. We have a few potential solutions for this, but the most plausible is we would allow for one form per issue type in the given project. Would this be a good solution?

2. Great to hear, we're currently working on improving the backend of the board which will allow us to bring over the new filters added to the other views. I believe this new board will be ready by the end of July and then filters could be a fast follow.

3. Awesome, sounds like you'd appreciate a timeline grouped by Assignee. @roto has explored this multiple times actually. 

@michael.helms you'll see this in the next week or so :) 

[Aaron Morris]

My wish list is all around list organization:

• Ability to configure Quick Filters on either the board view or list view (similar to Jira Software)
  • Quick filters on custom drop-down lists (single-select) (4 pts)
  • Quick filters on the Labels field (3 pts)
• Ability to configure swim lanes based on custom fields in the board view (4pts)

Context:  We're planning a move from Jira Server to Jira Cloud.  Jira Work Management seems like a great fit for many of our teams, and it's maybe even a selling point to expedite the migration.  However, we often end up with 100+ open items per project.  (good or bad, it's the reality.)  There's no way a JWM project with this magnitude of tasks would be usable without improved organization.  (Note:  My feedback is biased by my experience with Jira Software.  So if you're working on new ways to work with large quantities of tasks, we're open to new ideas.)  Thanks!

[Aaron Morris]

A little more context:

We currently use more traditional Jira Software Kanban boards for our task management projects.  We use custom drop-down lists and/or Jira labels to track customer accounts, requesting organizations, etc.  For example, there might be a task to produce a configuration specification report, requested by the Delivery Team, for Customer XYZ.  If we have an active engagement with Customer XYZ, then the team may have a swim lane or quick filter setup to show all open tasks associated with that customer.  They won't have a separate project for Customer XYZ, because a single team may support 10+ customers at a time, and they need to manage all tasks in a single place.

[Marie F. Kent]

Allow users to add columns to the List view. For example, Start Date and Remaining Estimate are not options. Ideally it would be very similar to adding columns in filter results. Score = 4. Feel free to contact me. Thanks!

[Chase Wilson]

Hey @Marie F. Kent , thanks for chiming in! I believe users should be able to do this already (and start date is rolling out to all projects by default soon). They can use the Plus Sign off to the right of the list to add said columns. However, users can only add columns (aka Fields) that already exist in the project.

One other caveat is that the field type must be supported for the project. We now support most of the popular field types, but not all of them quite yet. With that said, Start Data and Remaining Estimate are both fields using field types that we support.

If you don't see this working in your project right now, feel free to email me at cwilson@atlassian.com and we'll get it sorted for you 

[Marie F. Kent]

Thanks @Chase Wilson  My follow-on  request is the ability to rearrange the columns :)

[Aleksandrs Lozovs]

Supporting on that. Components column would be great additions. We have hundreds of labels, they tend to mess-up, but Components are configured per project which can limit the options. Also Components are being reported at Summary\Statistics page, yet they are not added anywhere else by default (default field for a ticket, hidden if not used)

[Chase Wilson]

@Marie F. Kent ask and you shall receive – we just prioritized column re-ordering (via drag-and-drop) for our current sprint. You should see it live in your instance in the next 2-4 weeks!

@Aleksandrs Lozovs you'll see Components even sooner than the above feature if all goes well. We're already testing that functionality in our team's instance. 

Cheers!

[Marie F. Kent]

Yes!

[Kathryn Minczuk]

@Chase Wilson I'd like to add onto this request, the ability to hide the # Key column. Thanks!

[Curt Holley]

• What @Dave Liao said ☝ and the ability to designate issue type for a form. 2.5
• Ability to nest across Jira hierarchy (from Epic to sub-task would do) in Timeline and Board view. 3.5
• Ability colour code by various options (not just status) on the calendar view particularly, but could be cool on other views as well. 3
• Ability to save views on Board, timeline and calendar (similar to how a view can be saved in Advanced Roadmaps) 2

[Dave Liao]

Ooh, I like the subtlety of the point-points! 

[Chase Wilson]

Hey @Curt Holley ! 

• Perfect, this is our current preferred solution – one form per issue type per project
• Coming this week for Timeline (Issue --> Subtask) and shortly after for List (Issue --> Subtask). We'll also start showing Subtasks on the Calendar (without hierarchy), and then start looking into Epic --> Issue --> Subtask on the List. Adding three levels of hierarchy on the Timeline is actually going to be quite difficult for us to pull off, so would a rotating hierarchy level work instead? It would effectively recognize the highest level of hierarchy in your project and nest things accordingly. E.g. a project with Epics would go Epic --> Issue and one with only standard Issues and Subtasks would go Issue --> Subtask. Thoughts?
• Interesting, any thoughts on what else you'd like the colors to correspond to? Teams or Issue types, for example?
• Awesome, we're actually exploring this right now. @roto let's reach out to Curt for prototype testing.

[Curt Holley]

HI @Chase Wilson 

All great news. 

Regarding Calendar colour options....custom field springs to mind as well as Labels and maybe even issue type.

Whilst on issue type on the calendar view....what would really help me today would be the ability to filter on the Calendar by issue type. I'd give that a 3.5

Regarding nesting, personally I would rating Timeline and Board of higher important than List view....But let's have it (or have it as an option) on all 😀👍

Absolutely feel free to reach out...happy to help forge the future. 

[Chase Wilson]

@Curt Holley great news is that we are absolutely adding the ability to filter on the Calendar by issue type. Ideally you'll see that in the next couple of weeks as it's something we want for our own teams as well!

Re: nesting, adding it to the board should be doable but AFAIK it's not prioritized yet. I just sent an email your way so let's chat about this on the call (as well as calendar coloring options as we haven't explored that much yet either).

Can't wait to chat 

[Josh Baumgartner]

Hey @Chase Wilson ,

Any update on Issue --> Subtask hierarchy in the List view? Things get pretty disorganized without it!

1. JQL or expanded (especially component, labels) filtering across all view types: List, Board, Calendar, Timeline (3 points)

2. Epic support with Epic --> Task --> Subtask hierarchy in at least the List view (4 points)

3. Ability to create multiple views for all view types, nested together with the ability to name, reorder, etc. these views. This would be huge for reporting and running meetings. (3 points)

[Ryan Smith]

@Chase Wilson The product roadmap shows that the ability to see and edit 3 levels of hierarchy on the List view was coming Q3. Is this feature available now? Or is it now coming in Q4? 

Edit: Please disregard. Reached out to admin, and it had to be turned on at that level.

[Alexandre Thouin]

Can you elaborate on how it could be turned on ? I really want to do the 3 levels !

[Ryan Smith]

@Alexandre Thouin Our Jira admin was able to configure Epics for our projects, but looks like the Q3 update for nesting hasn't been released yet (unless our setup is incorrect). Epics still don't work well in Jira Work Management . @Chase Wilson Any update on Epics nesting in the list view hierarchy?

[Brian Clair]

I wish we could hook up external Office 365 calendars into a project's Work Management Calendar. 

Rank: 3

Open to questions - yup

Why? - To make it easier to give broad visibility on company wide release dates (which can change frequently) into specific projects. For example, I'm setting up a QA request project and it would be great if I could hook the Work Management calendar into our company's overall O365 calendar so that all the dates are easily visible.

[Kathryn Minczuk]

Marketing - @Chase Wilson 
Product - @Ron Levy 
Design - @roto 
Engineering - @jtblin ︎ 

Hello, 

My organization is new to JWM, though we have been using Jira Software for years. We have a variety of types of projects, teams, departments, and organizational goals that we would like to track in JWM. 

Is it possible to create a level of hierarchy above Project? With a wide variety of projects and work that needs to be tracked, we would like to be able to group our projects by department, team, or client to easily organize this information. 

Thanks!

[Amelia Giuliani]

My team has ended up throwing all our projects under one project and using different ticket types, workflows, and components to track the progress of each one since I didn't want to have that many projects just for my team... especially as more teams in my organization start to use JWM. 

It works alright, although you often have to go to the advanced filters to separate out by component or go to the component section to see all the issues for that component. 

[Amelia Giuliani]

Feature 1: Ability to easily have non-JWM users create issues

My entire company uses Confluence and I would love it if anyone would be able to make an "issue" on my team's board. I know there is the issue collector but I've tried to embed that into a Confluence page using an HTML macro and I just can't get it to show all the fields to non JWM users. 

Why: I'm a learning and development manager. I want any employee or team to be able to request trainings or videos from our team in an easy way so that requesting training isn't another barrier for learning. Right now my IT team is investigating using Microsoft forms but it will require another subscription and it has be owned by an individual not a team. 

Score = 4 

Feature 2: Have More Security Permission Levels

I am a manager on a team that has one project in JWM. I want to be able to edit my projects workflows, add custom data fields, and change what the create issue pages look like without the ability to edit everyone else's projects. My IT team couldn't find a way to grant me access to setting that would only impact my project. 

Why: My two options are, beg my IT team to give me more access to everyone's projects at the risk of gaining more tasks I don't want to do or have power I really don't want OR constantly request that my IT team update this workflow, or change this wording, or add a field here which once it's set up will be fine but in the mean time we are finding new things we need added, etc. all the time. 

Score = 3

Feature 3: Do More with Components

Right now Components seem like a step down from labels. It would be nice if it was easy to filter boards, timelines, list and calendars by components, and see more component reporting widgets, etc.

Why: I'm using components as overarching goals, major projects, or pillars of my department. It would be nice to be able to more easily filter by that option. I currently have to go to the advanced search for it. It would be nice to see pie chart of task/issue statuses, % complete, etc. in addition to the number of tasks on the component page. 

Score = 2

Feature 4: Change the word "Issue"

Maybe it's just weird for my team but we are using this as a task management system to manage what we need to or want to accomplish and what are next steps are. They aren't issues or problems - they are to dos, tasks, requests, etc. 

Score = 1 (It's really not necessary it just feels weird)

Feature 5: Add Color and Personalization 

I love that you can change the icon but it would be nice if you could also set the background color for an individual project or have headers, etc. so that if someone is looking at one project and move to another they visually see they are in a different place. 

Score = 1 (It's not necessary, it's just one of those things that make it feel nice) 

Thank you!! 

[Paul Salais]

@Amelia Giuliani completely agree with all these recommendations. Our team feels similar pain. As a marketing team, we've bucketed our work using components and would appreciate a better spotlight. They appear to be an enhanced version of labels but not fully developed for business projects versus software projects. Thanks for sharing your feedback!

[Kathryn Minczuk]

Agree with this list also! Would love to be able to personalize structure vocabulary for each project as needed - Issue = Phase, Subtask = Task 

[Michael Bell]

Late to the party, but the only thing keeping me from full-fledged frontal assault to get my company to adopt the entire Jira ecosystem is the lack in JWM (or any of the Jira products as far as I can find) to do resource planning with per-person resource availability and concurrent assignments (Like 60% on task 1 and 40% on task 2).

[Jordan Taylor-Bartels]

Couple of asks here...

We're a digital lab that works on individual clients across "always on" type stuff as well as sprints for "campaigns. Currently migrating (or more so exploring the transition) to Jira WM. However, two core features are required to make this work.

1. In the list view, are we able to group issues/tasks under sub-headings underneath the project? i.e Phase 1, or Planning/Strategy etc. Simply, having sections?

Simply, it could even be to group them under a label? Asana does this currently...

Feedback Rating: 5

2. A macro (i.e Mission Control) view that allows certain leaders to see all tasks (in a list) within the company grouped by Project.
This is particularly handy for all-hands WIPs where macro visibility can be seen.

Feedback Rating: 5

Keep up the great work; but these ones are deal-breakers for us (and I'm sure many others)!

[Paul Salais]

Adding Components to an Initial Issue Entry Screen and Forms

1. I'd like the ability to add components to the initial issue entry. Our marketing team groups large buckets of work types by using components (i.e. brand, social media, website, etc.).
2. Feedback rating: 3
3. Yes, please feel free to contact me directly! 
4. Bonus: it's needed because our marketing department buckets priorities through components. Unless this is an administrator setting, components are not available on the original creation of an issue.

[Helen Stange]

This might be an annoying answer because it's not feature related, but I have various teams in my organization (1300 employees total) who want to use Jira Work Management because they've heard about it, but don't know where to start. It's easy to find hypothetical use cases
(https://www.atlassian.com/software/jira/work-management/examples), but I want to see how real organizations use the tool, exactly how they implemented their solution, and why their new set-ups beat their traditional ways of doing things.

This tool is so new that I'm not easilly finding these resources. I don't just want to hear that Company X used Jira to improve their Onboarding Process; I want to see how they did it. 

I feel like if people can actually see this in action, they can make the first step to using the tools. Is there a page you can link us to? Many thanks :)

[Chase Wilson]

We did say Ask For Anything, so this is fair game  We're planning on investing a good amount of resources in the next couple of months to build out content like this. What's interesting to me is that you mentioned it's your users looking for this content – with that in mind, would content that goes into the granularity of setup be less useful than how it's used and the benefits?

[Helen Stange]

Good question - the teams want it, but it's for me to onboard them and recommend what works best for their requirements ;)  I'd love to see all the creative use cases so that I can recommend the best templates and easily onboard each unique team with their unique set-ups.

I'm sure the various teams have use cases that could be solved using the exitsing templates, even if the templates aren't named that way (ex. Onboarding template could be used for other purposes)...

Thanks for your response, and looking forward to the resources over the next few months!

[Kathryn Minczuk]

@Chase Wilson My organization is in the same boat! Exciting that this content is being built out. Any updates on the timeline for some of these examples real world use cases?

[Lucinda Pagett]

Hi @Chase Wilson 

I think we've discovered a glitch/bug in Jira Work Management Cloud.

My team and I are having issues with the "Assigned to Me" filter. When we click on it in the List View, it only shows us a few of our assigned tasks (no all of them).

If we go to the advanced filter and enter in a date range and then click on our own name as the assignee and click "Apply". Then if we clear the date but leave the assignee field as my name and click "Apply", all my tasks come up.

If I clear the field and click on "assigned to me" filter on the main screen, it doesn't work.

Is there a way to fix this?

Thanks,

Lucinda

[Michelle A Johnson]

I would love a way to customize the view all projects screen. I would like the project creation date most!

[Ben Weinberg]

Ability lock down the board view. Not allowing users to rearrange to column order.

Give us all the board functionality we get with Jira software (minus sprints obviously)

4

[Lísa Jóhanna Ævarsdóttir]

1. Add a feature for external user to access 
   Users would be added on a project and would have restricted access. Users would be suspended when project is finished. Preferably license fee free users.
2. Rating 5
3. Yes
4. We work on projects with our external customers who need access to their projects while it is being worked on.

[HANUI KIM]

Please help me find a way to fix the list view of a project in Jira Work Management for all members of the project.

• I was able to create/add new fields for a new project
• I could edit columns to have the additional fields that I created appearring on the list.
• Now I have an organized list customized for the new project
• As an admin, I thought my view of the list could be shared with the members
• But it seems every member of the project should do the same job of 'adding fields, rearranging columns' to view the same list that I'm looking at 

How can I fix the list view for all the members of the project?

[Alex Janes]

Probably low on the Atlassian priority list, but...

How about availability of Jira Work Management on Datacenter? :)

[michael.helms]

If a task has subtasks, there should be an option to pull information from the subtasks: 

• If subtasks are "In Progress", the task is "In Progress"
• Task due date automatically updates to final task due date

[Jesus Kiteque]

Please add the remaining visualization options beyond the Board View to the Mac App.

[Marie F. Kent]

@Chase Wilson ,

Not really a requirement, but a question. During JWM project creation, the user is prompted to select a team. Drop down is called 'What team is this for?'

What is the purpose of this field? I cannot locate any documentation on it and it does not appear in the project settings. 

Thanks!
Marie

[Chase Wilson]

@Marie F. Kent this field is actually just for internal data collection and has no impact on your instance – here's a Community post giving a little more information on the topic. 

[Dave Liao]

@Chase Wilson - I'd love to have infinitely-customizable background colors. The default 14 colors aren't bad, but I'd love the option to choose any color I want. 🎨

Score = 4 😉

[Chase Wilson]

Wow, 4 for background colors! How about images? That's what @roto sends back my way whenever I tell him we should add more colors  . In any case, I believe we're considering more of a color wheel approach instead of stock defaults so that companies can add more of their branding to projects.

Quick note, accessibility is something we take seriously when designing and the current colors were chosen in part to keep text easily visible no matter the color choice. That's why we didn't begin with the "choose your own adventure" until we could explore this a bit more.

[Dave Liao]

I did think about images (a la Trello board backgrounds) but wanted to keep my feature request atomic. 😉

Obviously trolling with the score. "4" as in, I'd use background colors if we liked any of the default colors. haha

More precise feedback: most of the background colors (especially the darker ones, but not limited to them) make the built-in Jira sidebar icons hard(er) to see. 

[Marie Peters]

• I'll second "Ability to nest across Jira hierarchy (from Epic to sub-task) in Timeline and Board view". I'm also using Advanced Roadmaps so having that hierarchy reflected on the Advanced Roadmap would be key. 4 (It's not enough to keep us from using JWM but I would be ecstatic if this was added!)
• Additional custom field types, along the lines of what's available for a Jira Software project -- in particular, cascading select fields or even just a dropdown field would be super helpful. 3.5

I'm managing different types of projects across multiple teams, and more granularity in terms of how we categorize things would be super helpful. We also have a predefined taxonomy that we're working with, so I'm trying to jam that onto JWM using Components and Labels. But it's difficult without dropdowns (Labels are a bit too freeform for our needs but we're making do) and with the lack of a hierarchy for epics/stories/etc..

Thanks! Feel free to contact me!

[Curt Holley]

Hey @Marie Peters 

Because JWM project are Company managed projects, you can visualize their content in Advanced Roadmaps. This is a way to get the hierarchical structure visible from your JWM projects.

Here is a real life example of Epic, to (in this case custom issue type of Release) Story level with sub-tasks

[Marie Peters]

Ah! I tried to nest things on the Advanced Roadmap by clicking and dragging, but I couldn't get it to work consistently. And then I couldn't see the relationship when I went back into the project, so wasn't sure it 'stuck'. I will play with it again!

In my perfect world the person who enters Epics/Issues on each board (not me) would nest all the things and they would just appear nested in the Advanced Roadmap. But I don't think it works that way today?

Thank you, Curt! :) 

[Curt Holley]

That is how it works for me/us @Marie Peters 

What is the issue source for the plan? For the above I simply used the whole Project. Although the hierarchy is not all that evident in the JWM project itself, it falls right into place in AR.

Note: I did have to add Epics and the Release custom (story level) issue type into the JWM project to achieve this.

[Marie Peters]

Oh! I get it now! I just played around with it and got it to work :) I was going at it the wrong way, heh.

Thank you so much! So really all I would like around this point is the nesting relationship showing up on Boards and Timelines, and my rating would drop to a 3

Thanks again!!

[Chase Wilson]

Thanks for the help @Curt Holley and cheers for participating @Marie Peters ! Let's dig into this a bit.

• Hierarchy: Major focus for us and the team right now. This week you'll see (if you don't already see it) nested issues on Timeline (Issue --> Subtask). Fast follow will be List hierarchy (Issue --> Subtask) and then, potentially, three levels of hierarchy on the List (Epic --> Issue --> Subtask). How important is nesting on Board for you vs List? We find the List view to be more user-friendly for viewing and changing lots of data.
• Custom fields: You got it  Right now we're adding component, url, select, multi-select, date, and date-time as newly supported field types for the list. We'll continue to gradually add support for more field types!

[Lucinda Pagett]

Hi @Cha

I also would love the hierarchy feature on JWM. Team I work in is currently transitioning to JWM and our board and lists are a mess because we can't connect Epics with their sub-issues.

My team finds both the list and the board view hierarchy the most important as they are good overviews to track each project.

Do you by any chance know when this could come in? I don't know if I can onboard my whole team without it because it will fill our boards too much with all the sub tasks.

Thanks,

Lucinda

[478 Fatihah]

hello guys, can someone help me with this issue.

retrieve the details of jira comment by using the automation. im using app script to retrieve the data from jira comment. i want to set the every latest comment into my spreadsheet. but the problem is, only get text and first link. text after the link will not appear on my spreadsheet. 

i want that fully content of the latest comment insert to my spreadsheet