Project Management Template create columns that can create tasks

[Lenin Falconi]

Hi, there I am new to this Jira World. I found very interesting the Project Management Template to trak a project I am directing. However, the template even though it lets to create new columns. I have noticed that only the ToDo Column is able to create issues. Any new column is not able to do it. Consequently, my question is how do I edit this behavior so that I create a new column which can create issues? I have checked to edit workflow but nothing has worked.

On the other hand I have noticed that Kanban templates allow to build any issue in any column but lack the view like list and calendar. So if the former is not possible How can I add to Kanban project the missing views that a project management template has?

[Arthur Gonçalves · Accepted solution]

This problem has been solved by Atlassian Support team upon following the instructions on the following knowledge base article:

https://confluence.atlassian.com/display/JIRAKB/Edit+or+Update+Issue+results+in+a+NullPointerException

Cheers!

[Nic Brough -Adaptavist-]

If you're getting a red box and no error message, then you probably want to read the application log to see what the (hidden) error is.

(I'm also a bit confused on those ticket numbers - they don't look like Jira references)

[Molly Favret]

We changed the requirements for the project key to allow numbers, which is one of our requirements. How can I read the application log? I don't have access to the server.

[Nic Brough -Adaptavist-]

I'm afraid you're probably a bit stuck if you don't have access to the server - you need to ask your server owners to get you the log file because you almost certainly need to see it to debug this problem.

You could try raising a support request from within Jira - that will read some of the log file information as it logs it with Atlassian.

Your change of key could actually be the problem too - I know there are problems in Greenhopper if you allow numeric keys in some versions. More to the point, I know that starting a project key with a number causes some issues in common plugins and in some of the core functions in Jira as well - that's why I asked - from long bitter experience, I know never to start a project key with anything other than a letter (although everything I've worked with has been fine with numbers elsewhere)

If you need to log this with Atlassian, you could well be asked to move the issues to a project that has a standard key pattern before they can help you.

[Molly Favret]

I cannot change the project key requirements and actually consulted with an Atlassian partner on this change. The thing thats odd is that we have hundreds of tickets across 80+ projects using this same key structure and have not ran into this issue. I can't find anything different about these 3 tickets. I have already raised a support ticket, so hopefully someone will be able to help. Thanks for your thoughts!