Cannot add columns in next gen but in Jira classic

[Katja Demuth]

Hi there,

I am currently trying to solve an issue with columns in next gen projects. I already searched though older posts but they delivered no solution.

I am not able to add or rename or delete columns on a next gen project. However, I am able to do all this in a classic project.

So I don't consider the cause of the issue in administration problems. I am the only user in my organisation tho, so I am administrator, project owner, board owner, etc.

Currently I am using the free version of Jira Software.

No board settings / or the "+" symbol to add a new column in Jira next gen project:

Board settings available and the "+" button to add new columns in Jira classic project:

Any ideas or solutions to solve this issue?

Thanks in advance
Katja

[Nic Brough -Adaptavist- · Accepted solution]

Your two projects appear to be different types - one is software, the other work management.  

Work management project boards are not configurable, they draw their config from the project, that's why you're not seeing the settings in there.

[Katja Demuth]

Hi @Nic Brough -Adaptavist-

so is this the case for every other project except software projects (like marketing projects or project management)? Because I can‘t edit columns in any other next gen project either (except Kanban/software).

Even when I choose an empty template, so no Jira template at all, I can‘t add new columns to any next gen project.

[Nic Brough -Adaptavist-]

It's a bit more complex as there are many ways to configure projects and boards are not necessarily linked to the projects directly.

It's easier to talk about the board than the project types when explaining this. 

• Some boards are very simple - Jira Work Management projects have a single and very simple board attached to them, one that does not have any configuration at all.
• Jira Service Management projects do not have a board at all (but you can get them)
• Jira Software projects do have configurable boards, but they are very different for Team-managed projects and Company-managed projects.  Team-managed projects again only allow for one board in the project, and for most of these, the configuration is nothing more than column mapping
• And there is one last important quirk - a company-managed project, although created within the context of a single project, can include other projects. 

In short, you can't configure the columns in your team-managed project because it is not a Software project!

[Salman Ahmad]

Thanks a lot for your information. I am just curious which step should I Follow First for the better result?

[Matthias Gaiser [K15t]]

Hi @Katja Demuth

welcome to the Atlassian Community.

The team-managed (next-gen) projects work in a bit different way than the company-managed (classic) ones. Are you able to add new columns following these steps?

1. Click on Project settings (Projekteinstellungen)
2. Click on Board > Columns and Statuses (Board > Spalten und Status)
3. Here you should be able to add new columns and map the statuses to the columns.

Does that work for you?

Cheers,
Matthias.

[Katja Demuth]

Hi @Matthias Gaiser [K15t],

thank you for your fast reply.

I am familiar with the differences between next gen and classic, but it should be possible to add columns in both versions according to my research. That isn't the case with my account.

I can‘t click on board settings, because I have no options accessing the board settings in the next gen project. Please see the screenshots attached to my reply.

Within the Project settings there are no board settings. I can only change the name of the project there, the picture and switch to another project owner if there would be other people in my organization.

However, board settings are available within the classic project.

Kind regards
Katja

Next gen project (no board settings like columns):

Classic project (board settings with column settings available):

[alex-chz]

to be frank, i am quite curious, whats behind the scene over this over complication of the processes with tons of templates? Why some things are available for particular  project templates, while other things are disabled completely?  E.g to be frank i still can not get the idea behind the scene, why you can not just add columns in any project types and map to ticket types you wanna see there. I used in the past on-premise version and there had no any issues.  IMO, who cares about project type or so.. Its just a board. Its purpose to render tickets in particular statuses in the columns, nothing else :D

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

The logic behind it is that the four main Jira products are for doing different things.  Jira Work Management, Jira Software, Jira Product Management, and Jira Service Management are all intended to support very different types of team.

Jira Software boards are the most configurable ones of the four, and those are probably what you used before.