can not upload the Agile Maturity Matrix into JIRA v7.1.0

[ALO]

Hi,

I want to import the Agile Maturity Matrix into JIRA according to this guide:

http://blogs.atlassian.com/2013/11/agile-maturity-how-agile-is-your-organization/

I get this error:

"For the CSV import to be successful, you must specify a CSV header row that corresponds to the Project type. Available project types are: software, business."

Apparently the Project type is missing in the CSV File, which is dated to 2013...I added the Project type and I entered the value "Software" or "Business" in that column, but it still doesn't work:

"An invalid project type was specified. Unfortunately you can't create a project without a project type. Please talk to your JIRA administrator for help."

Any idea how to make this work?

Many thanks!

Best regards,

Loredana

See attachment:

[Tarun Sapra · Accepted solution]

The project type seems to be "Business projects" instead of just "Business" and "Software projects" instead of just "Software"

[ALO]

Thank you Tarun. I tried with "Software projects" and I get the same errors:

"An invalid project type was specified. Unfortunately you can't create a project without a project type. Please talk to your JIRA administrator for help."

"Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters."

"Invalid project name Agile Maturity Matrix,Software projects,AMM,52,2,"Big ticket, whole project. Full requirements document with corresponding estimates required prior to funding. Bake-off between projects to determine which projects get funded. Project success dependent on fully implementing all requirements.",Sub-task,Impeded,: The project name must not exceed 80 characters in length."

"Invalid project name Agile Maturity Matrix,Software projects,AMM,56,6,"Rarely raised out of ambivalence, belief that they will be ignored or other reasons",Sub-task,Impeded,: The project name must not exceed 80 characters in length."

and so on...

[Tarun Sapra]

Can you share the CSV header which you are using.

Something similar - https://jira.atlassian.com/browse/JRA-45676

Here in JSON they have used just "type" instead of "project type"

[ALO]

I attached the matrix CSV to my first description. I tried with "Type" in the CSV file which I then assigned to "Type" at the mapping page, then I get:

"For the CSV import to be successful, you must specify a CSV header row that corresponds to the Project type. Available project types are: software, business."

or assigned to "Project Type"...same errors as:

"An invalid project type was specified. Unfortunately you can't create a project without a project type. Please talk to your JIRA administrator for help."

"Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters."

"Invalid project name Agile Maturity Matrix,Software projects,AMM,52,2,"Big ticket, whole project. Full requirements document with corresponding estimates required prior to funding. Bake-off between projects to determine which projects get funded. Project success dependent on fully implementing all requirements.",Sub-task,Impeded,: The project name must not exceed 80 characters in length."

"Invalid project name Agile Maturity Matrix,Software projects,AMM,56,6,"Rarely raised out of ambivalence, belief that they will be ignored or other reasons",Sub-task,Impeded,: The project name must not exceed 80 characters in length."

and so on...

[Tarun Sapra]

Currently you have a Typo in your CSV , it says - "Project Tpye" instead of "Type" it's "Tpye"

[ALO]

Well seen! I corrected that and tried with:

"Project Type" - "Software", "Project Type" - "Software projects", "Type" - "Software"....

I still get 100 errors like:

An invalid project type was specified. Unfortunately you can't create a project without a project type. Please talk to your JIRA administrator for help.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,52,2,"Big ticket, whole project. Full requirements document with corresponding estimates required prior to funding. Bake-off between projects to determine which projects get funded. Project success dependent on fully implementing all requirements.",Sub-task,Impeded,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,56,6,"Rarely raised out of ambivalence, belief that they will be ignored or other reasons",Sub-task,Impeded,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,65,1,"There is understanding that structuring the organization around products, teams, and delivery is better. Some changes have already been made and more are underway.",Sub-task,In Transition,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,66,2,"Some portions of previous state only partially required. For instance, project is broken up into multiple releases and changes to requirements are encouraged or only 50% of requirements need to be fully estimated",Sub-task,In Transition,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,67,3,"The number of projects in progress is known, there is some upper limit on how many can be in progress at a time, and that limit is usually enforced.",Sub-task,In Transition,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,68,4,"Delivery based metrics are being tried, planned, or discussed",Sub-task,In Transition,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,79,1,"There is consistent effort applied to moving to a product, team, and delivery based organization",Sub-task,Sustainable,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,80,2,"Projects are funded on a quarterly basis, only a quarter's worth of scope is needed at a time, and a significant criteria for success is the amount of shippable product produced",Sub-task,Sustainable,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,86,8,"Adoption goals have been set, progress is tracked and frequently influences the behavior of the organization",Sub-task,Sustainable,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,88,10,"50%+ of teams are operating at at least stage 3 of self-organization, most teams are being encouraged to get to stage 3",Sub-task,Sustainable,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,93,1,"50%+ of the organizational changes required to move to a product, team, and delivery based organization have been made and the rest is actively in progress.",Sub-task,Agile,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,102,10,"70%+ of all teams are operating at stage 3 of self organization, 50%+ of all teams are operating at stage 4 of self organization, all teams are being encouraged to get to stage 4",Sub-task,Agile,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,103,11,"Product owners are fully available to teams, empowered, and well trained in their role",Sub-task,Agile,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,107,1,"Product, team, and delivery based",Sub-task,Ideal,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,112,6,"Strong culture that encourages the finding, raising, and rapid addressing of impediments",Sub-task,Ideal,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,122,16,"Blame game, finger pointing, denial, anger, shouting, backstabbing, passive aggressive, turn-over and other behaviors on a regular basis. Desire to go back to the old ways, active resistance to change, scapegoating. There is churn or people are frequently making references to quitting or how much they dislike their work or work environment.",Sub-task,Impeded,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,126,16,"There are still elements of previous state, but there is steady progress away from those behaviors, problems are being actively addressed, and there is a general feeling that morale is improving",Sub-task,In Transition,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,128,18,"Some defacto team norms that are generally recognized, but haven't yet been written down and agreed on by the team.",Sub-task,In Transition,: The project name must not exceed 80 characters in length.

Invalid project key null: Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.

Invalid project name Agile Maturity Matrix,Software projects,AMM,129,15,"80% of the team can explain the benefits of Agile, believe in the benefits of Agile, understand the spirit of Agile. The team is making improvements on a regular basis",Sub-task,Sustainable,: The project name must not exceed 80 characters in length.

[Tarun Sapra]

Ok, please try this now, Create an Empty project in JIRA called "Agile Maturity Matrix" with a proper Key and remove the columns "project type", project key and project name from CSV and import the issues in the existing project, that should work.

[ALO]

Ok, the import worked but has many errors:

Import completed with 65 errors:

• Error importing issue [externalId='52,2,"Big ticket, whole project. Full requirements document with corresponding estimates required prior to funding. Bake-off between projects to determine which projects get funded. Project success dependent on fully implementing all requirements.",Sub-task,Impeded,', summary='null']
• Error importing issue [externalId='56,6,"Rarely raised out of ambivalence, belief that they will be ignored or other reasons",Sub-task,Impeded,', summary='null']
• Error importing issue [externalId='65,1,"There is understanding that structuring the organization around products, teams, and delivery is better. Some changes have already been made and more are underway.",Sub-task,In Transition,', summary='null']
• Error importing issue [externalId='66,2,"Some portions of previous state only partially required. For instance, project is broken up into multiple releases and changes to requirements are encouraged or only 50% of requirements need to be fully estimated",Sub-task,In Transition,', summary='null']
• Error importing issue [externalId='67,3,"The number of projects in progress is known, there is some upper limit on how many can be in progress at a time, and that limit is usually enforced.",Sub-task,In Transition,', summary='null']
• ....
  I'm checking it out. Many thanks for now for your support!!!

[Tarun Sapra]

Yes, the errors because of bad CSV, I can see locally row 66, 67 , 68 are all malformed thus the errors. Once you fix those columns it will work like a breeze, please accept/upvote answer. Thanks

[albinas.uikis]

Tarun, are you paid by Atlassin for the support? i really apologise if not because i have some issues with how Atlassin approach these things.

What happens if the user cannot make an empty project, and they want to use an existing project configuration and import issues into that. The original question was not answered and instead, a hack was proposed. This is not the way to do things because there are many Jira users out there with similar issues, and when they look for a solution to their problem, they will use resources such as this forum for help. When you propose a solution that is only going to help a subset of users, (i.e. users who are happy to create a blank project) then you are only serving to frustrate many other people who will look to this question for answers, and find none.

if you are employed to support Atlassin users, then please answer the original question, i.e. how does someone import issues (using CSV) into an existing project, where a project type has to be specified. 

[Nic Brough -Adaptavist-]

No, he's not paid.  We're a community of end-users trying to help each other out.  Atlassian are here and they do pick up questions.  You'll see their profiles are highlighted with "Atlassian", much the same way Tarun and I have "community champion"

For this question, the answers are there, but they are scattered through the conversation - it's one of the ones that has gone through several iterations.  The answer is not "create a blank project", but, in fact, "get your CSV correct"

[albinas.uikis]

Hi Nic, thanks so much for helping out then, to all of you guys. its a shame that Atlassin is so haphazard with their features and documentation. their official how to guides, docs and blog posts do not accurately describe how to use their software, one must be very knowledgeable or else rely on help from kind people like yourselves. I don't think it is the right way to run a SAAS company to be honest. but again, thanks for your help

[Nic Brough -Adaptavist-]

Well, you were reading a conversation ranging from 1-5 years ago. 

[carlos_marin]

@Loredana  Could you share your csv file?