Different lists with different columns for different needs: how?

[Emanuele Tonetti]

Hi, I am setting up a team-managed project and I would like to have different lists that have different columns/(custom) fields depending on what I want to see. 

Say that I have three Work Types and for each of them I need to see different columns/(custom) fields as they are structured in different way and so they contain different data points/info.

How can I achieve that?

[Daniel Franz - JXL · Accepted solution]

Hi @Emanuele Tonetti 

As Robert mentioned, there is only one List view and it cannot be duplicated or saved as several views.

If you're open to solutions from the Atlassian Marketplace, you might be interested in the app my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your Jira data that allows viewing, inline-editing, copy-pasting, sorting, and filtering by all your work items' fields, much like you’d do in e.g. Excel, Google Sheets, Smartsheet, or Airtable.

The view it provides in Jira is called a Sheet, and you can save and switch between as many sheets as you need, each with its own set of work items, column layout, bespoke work item structure, groupings, sum-ups, conditional formatting, etc. Just create the perfect list views individually for all of your use cases. And this is how it looks in action:

Any questions, just let me know.

Best,
Daniel

[Emanuele Tonetti]

That's interesting, thanks @Daniel Franz - JXL

[Robert DaSilva]

Hey @Emanuele Tonetti , if I understand correctly, you'd like to configure the visible dropdown lists based on the Work Type you're looking at? So, one work type would show one list, while a second work type shows a different list?

If this is the case, you can accomplish this through the use of unique Custom Fields, as well as a Work Type Screen Scheme.

1. First, I recommend documenting your goal, so we can keep track of what has been accomplished.
2. Next, create all of the unique dropdown fields you want to display.
3. We'll want to create a unique "Screen" for each work type, and work type action. You can create screens for three actions: Create, Edit, and View. Screens can be re-used for multiple if you do not need different fields to display for different actions. I recommend naming the screens based on the work type name, to keep things organized.
4. You'll want to create a Screen Scheme for each work type. This associates the specific screen with those specific actions I mentioned before (Create, Edit, View).
5. We'll want to create a Work Type Screen Scheme. This associates the Screen Schemes to be tied to the work type itself.
6. Finally, you'll want to associate this Work Type Screen Scheme to the Jira Space you're working in.

Hope this helps!

Robert

[Robert DaSilva]

Here's some great Atlassian Learning content that I recommend you review. https://community.atlassian.com/learning/course/configure-work-items-and-fields-in-software-projects

[Emanuele Tonetti]

HI @Robert DaSilva thanks for your answer. Probably I did not make myself clear. Here is what I meant:

I noticed that the List View can be only one and once I set its columns with the fields I want that's it. Say that I want to filter Work Type A and I have customized those columns for Work type A: that's great, but it would not be useful for Work Type B and C as I need to see other columns for those. 

I found a workaround by creating Filters, so that I can also customize columns for each and every filters, but I was hoping to have multiple Lists like that, you got what I mean?

[Robert DaSilva]

Hey @Emanuele Tonetti , I understand now!

To my knowledge, the List view can only be created once. What you could try is creating new "Boards". These would be a Kanban or Scrum view instead of a list, but would allow you to apply specific filters that would be inherent to the board itself.

You can do this by clicking the + icon beside the Jira Space name, and creating a new Board. You'll want to have pre-created filters that limit the view to only the work you want to see, so I'd recommend doing that first.

Otherwise, your filter approach is perfect for filtering down the main List view.