Hello,
I'm using the admin csv importer to bulk import issues from an external system.
In my CSV, i have two columns named :
The two fields (fixVersion and affectedVersion) are in the target project's configuration, and are on the create, view and update screens of the targets project.
I launch the import as admin, and in the target project, admin has all the permissions.
When the import is done, i noticed that both field are well filled with the values i got in my csv, but for the affectedVersion, it is not linked to the version.
fixVersion is filled with the good value and well linked to the version but not affectedVersion.
When i go to the Version screen, i have some version created by the importer, but with no issues inside.
I checked the mapping configuration on the import screen and both field are correctly mapped.
Does anyone has and idea on how to fix this behavior ?
Hi @Antoine B
To be honest I do not think that this is a bug. I think Affected Versions field were behaving differently than Fix Version field and not showing as "link".
Here are corresponding tickets
Hello Mirek,
Thank you for your answer. Does that also explains the fact that i have, in the version tab, some version created but on which Jira is displaying "no issue" like below?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Antoine B ,
Yes, from what I know basically by specifying “fixVersion“ for Jira issues you actually connect them to one of the versions.
If you look at JAC for example
You should notice also many No issues versions even is some versions are having only Affected Version associated with issue
Example for 9.9.3 version:
When you hover your mouse over the link it also gives you something like this
https://jira.atlassian.com/browse/JRASERVER/fixforversion/105836
so pointing to fixforversion..
Also official tutorial related to defining version says:
Affects version is the version in which a bug or problem was found. Although it can be useful for tracking problems, it isn't used very often in Jira.
Fix version is the version where you plan on releasing a feature or bugfix to customers. This field is used for release planning, monitoring progress and velocity, and is used widely in reporting. This is most likely the field you want.
So it's pointing to use FixVersion not AffectVersion.
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.