Bulk upload of dependencies

Question

Hi,

I have an ID column in csv. , and then created a Dependency 1, Dependency 2 and so, columns so each Dependency would have its own column.

I was under the assumption that if I mapped that ID column , that would be my parent ID. And I would use then the Link to Parent so all those tasks would be linked to the parent ones.

But I have an error on the validation saying that I dont have the sub task issue.

2022-02-15 19:00:34,990 WARN - Issue 'Current logic reroutes the alteration pipe, hence replacement logic in actions M019, M020, M021, etc' doesn't have Subtask Issue Type, its Parent Id mapping will be ignored.

I am sure someone already asked this. But I don't understand from the forums what exactly i need to to deal with dependencies on the bulk upload. I understand well how to do it after, but I am trying to avoid to do it manually one by one.

Could you please help me?

Trudy P Claspill · Answer

I work in Jira Cloud, and the functionality there is not exactly the same as Jira Server, but I did work with Jira Data Center 7.13 years ago.

I think you first need to figure out how you would define the dependency through the UI, because that will determine how you need to map fields in a CSV import.

When I worked with Jira Server/Data Center there was not native "dependency" functionality, as I mentioned. You could use the generic issue linking functionality to create a link between issues, and you can define different "types" of links (i.e. relates to, depends on/is depended on by, caused by/is caused by), but that does not inherently result in any special functionality being applied to the issues because of that link.

There are third party apps that you could add to your environment that might add features that provide functionality related to dependencies, but how those third party apps recognize issues are interdependent could be different than the built-in issue linking functionality.

Joana Pinto · Answer

I have a rule with an ID A11 for example, but there are other two rules that are dependent on the work of this one. I would expect to have somewhere in the UI the dependency and i know that is possible. I just wanted to do it in Bulk because I have one rule that is impacting 5 other rules and it can become very dull.

But that answer assured me that I was trying something not as simple as i thought.

Cheers for that! :)

Trudy P Claspill · Answer

Hello @Joana Pinto

Welcome to the community.

By default, Jira doesn't have a "dependency" relationship. You could use the Jira issue linking functionality to define that an issue is dependent on another issue, but there is not built-in Jira functionality that does anything based on issues being defined as dependent on each other in this way.

The Parent field is specifically used by a Sub-task type of issue to identify its parent issue. That is a special, built-in relationship in Jira, specifically used by Sub-task issue types and their parent issues. It can't be used to establish a generic dependency relationship.

How would you define a dependency between two issues if you were trying to do it through the UI? After you explain to us how you do it in the UI we will probably be able to advise you how to accomplish it through the CSV import.