Bulk Import using CSV not updating story point value. The story point value is in the CSV file. I've tried both the Map to Field checkbox checked and unchecked, that story point value still won't import and update accordingly. Remaining fields import just fine.... What am I missing?
Hello @robyn.graham
Are you importing data to a Company Managed project or a Team Managed project?
What are the issue types in your CSV file to which you have assigned Story Points?
Can you show us a sample of your import data and show us you field mapping from the Import wizard?
This is what my format looks like:
All field values import correctly and the bulk import wizard identifies it with the value in the csv file, but for whatever reason, once all the stories are created, the story point value remains 0. Thoughts?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you show us you field mapping from the Import wizard?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is how the mapping looks just prior to beginning the import process. And, even going to next screen, (captured below) to show the from/to values. It all looks correct. But, upon its completion, story point value is still 0.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First, you only need to use the Map field value checkbox if the value in the import file can't be added to the field as-is. For instance, if the field in Jira is a selection list and the values in your import CSV don't have a 1 to 1 correlation to the selection list values.
Story Points, Summary, and Description are not selection lists, so you don't need to use the Map field value option for them.
You probably don't need to use that option for any of your fields unless, as I said, there is not a 1 to 1 correlation between the values you specified in your import file and the values that are actually available for the fields in Jira.
I recommend you try importing without that option selected and see if that makes a difference for the Story Points field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bulk importing without ANY checkboxes chosen to be mapped. Everything was created, it starts to set the story points, but it ultimately changes it to 0. I didn't change it to 0. The import did. Any other ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That history entry is an indication that there is an Automation Rule changing the Story Points value after it has been imported.
If you click on the Rule Executions field under Details for that issue...
...then you will see a history of the Automation Rules that were applied to the issue.
If it is a project-specific rule and you are a Project Administrator for that project then you can go to Project Settings > Automation and review the details of that rule and modify it if necessary. If you are not a Project Admin for the project or the rule is a Global Rule, you will need to work with your Project Admin and/or the Jira Admins to review the rule and figure out if/how it needs to be changed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's exactly it! There is definitely a rule in there to 0 out story points that the admin must have put into place before me. I'll either resolve it or work with the admin on it. Your patience and continued response is very much appreciated! Thank you so much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.