Epic Link & Parent Link movement to Parent

[Magdalena Zhisheva]

Hi all, 

How did you get prepared for the Epic Link & Parent link removal and replacing them with Parent field?

I went through all documents but still do not get it, for example: https://support.atlassian.com/jira-software-cloud/docs/maintain-epic-link-data-for-issues-above-the-epic-level/ here, there is a script 

issuetype in (<LIST OF ISSUE TYPES>) and "Epic Link" is not EMPTY and I assume that we need to perform some changes in the issue types above our epics, i.e. in our case initiatives. 

But still I do not get what should be done. In the same page there is the following: 

Maintain epic relationships

There are two approaches you can take to maintain the epic relationships on affected issues:

• If your issue hierarchy is important in its current form, you can add the epic as a linked issue (e.g. relates to).

OR

• If your epic link data is important to maintain, you can move any affected issue types to the base level in your issue hierarchy.
  
  If we add the epics as a linked issue to the Initiatives we will use the hierarchy between them in Advanced Roadmap and we do not won't to have this case. Currently, we are using parent link for having the linking between Initiatives and Epics.
  P.S. Parent field can't be added to the project screens.
  
  So, the question here is how did you prepared yourself for these changes?
  Any directions will be useful!
  
  Thank you all in advance! 

[Leena Bakshi · Accepted solution]

RESOLUTION:

For us taking out the receiving squad unfortunately was not an option as other projects were loosing 100s of tickets. 

Even after giving permission to users on all the projects in our instance, it dint resolve the issue because we have 3 service desks so even after assigning manage sprint permission on the service desk projects , users were  not able to create/complete sprint. There is a bug reported for the same : https://jira.atlassian.com/browse/JRASERVER-64899 

I did the following to resolve the issue:

1. Created a group and added all the users who are facing issue in managing sprint.

2. Added this group in all the permission schemes including the one being used for Service desk( even though Service desk permission overrides the manage sprint permission)

3. Edited the board filter as follows so that we dont include the projects from the service desks:

((project = SUB AND issuetype not in (Test, "Test Scenario") OR project = SUB AND "Receiving Squad" not in ("MO Ops", "Data Ops", "Bl Ops", "Int Ops") OR "Receiving Squad" = Sub) AND status != Resolved) AND Project not in (SD1,SD2,SD3) ORDER BY Rank ASC

Now users are able to create sprint.

[Leena Bakshi · Accepted solution]

RESOLUTION:

For us taking out the receiving squad(custom field) unfortunately was not an option as other projects were loosing 100s of tickets. 

Even after giving permission to users on all the projects in our instance, it dint resolve the issue because we have 3 service desks so even after assigning manage sprint permission on the service desk projects , users were  not able to create/complete sprint. There is a bug reported for the same : https://jira.atlassian.com/browse/JRASERVER-64899 

I did the following to resolve the issue:

1. Created a group and added all the users who are facing issue in managing sprint.

2. Added this group in all the permission schemes including the one being used for Service desk( even though Service desk permission overrides the manage sprint permission)

3. Edited the board filter as follows so that we dont include the projects from the service desks:

((project = SUB AND issuetype not in (Test, "Test Scenario") OR project = SUB AND "Receiving Squad" not in ("MO Ops", "Data Ops", "Bl Ops", "Int Ops") OR "Receiving Squad" = Sub) AND status != Resolved) AND Project not in (SD1,SD2,SD3) ORDER BY Rank ASC

Now users are able to create sprint.

[Nic Brough -Adaptavist-]

The "or 'receiving squad' = " clause implies "any project where the 'receiving squad' field is valid.  Hence many, if not all, of your projects could be included.

Try limiting that clause.  For example:

project = SSRF or ("Receiving Squad" = "Project name" and project in (WEB, SSRF) ) ORDER BY Rank ASC

[Leena Bakshi]

Current Filter is :

project = SSRF or "Receiving Squad" = "SIM-493: Sap Re Implementation" ORDER BY Rank ASC

where in SIM-493: Sap Re Implementation is SSRF project only.

[Leena Bakshi]

sorry for not mentioning earlier. Receiving squad is already limited to the current project of SSRF

[Nic Brough -Adaptavist-]

It doesn't matter - the receiving squad field could be in any project.

[Nic Brough -Adaptavist-]

Ah, your mail crossed over.

If "recieving squad" is limited to the SSRF project, then the clause is irrelevant - anything with "SIM-493..." is, by definition, going to be caught by "project = SSRF".

In that case, I'd cut the filter down to "project = SSRF" - then Jira won't be looking for other projects at all.

[Leena Bakshi]

Right.. thats what I thought too. but even if I leave the receiving squad alone, it should still work.. shouldnt it? because anyways it is exclusively looking only for the same project in both the keywords?

Plus it was working for user AB.CD a few days ago

---

That being said, exact same issue is happening with this query also :

(project = SUB AND issuetype not in (Test, "Test Scenario") OR project = SUB AND "Receiving Squad" not in ("MO Ops", "Data Ops", "Bl Ops", "Int Ops") OR "Receiving Squad" = Sub) AND status != Resolved ORDER BY Rank ASC

When I run this query, it pulls up all SUB project issues only.

and the user is board admin and project admin.

user is not able to create sprint.

[Nic Brough -Adaptavist-]

You're drifting off-topic now.  Let's concentrate on the first problem instead of wandering on to another one.

What happens if you change the board filter to just "project = SSRF".  Can your user create the sprint now?

[Leena Bakshi]

I have yet to suggest this to the user. Will update you once done. 

Thanks

[Leena Bakshi]

Hi Nic,

Happy New Year

First user removed the "Receiving Squad" field from the board filter then  he could create the sprint. and he lost only one issue. so the original issue of this question is resolved.

The approach worked with another user also however she ended up loosing 100s of issues because of the modification in the board filter.

Old Board query:

(project = SUB AND issuetype not in (Test, "Test Scenario") OR project = SUB AND "Receiving Squad" not in ("MO Ops", "Data Ops", "Bl Ops", "Int Ops") OR "Receiving Squad" = Sub) AND status != Resolved ORDER BY Rank ASC

New board query:

(project = SUB AND issuetype not in (Test, "Test Scenario") OR project = SUB AND "Receiving Squad" not in ("MO Ops", "Data Ops", "Bl Ops", "Int Ops") ) AND status != Resolved ORDER BY Rank ASC

As per Atlassian document ( Manage Sprint permission for advance cases) is to give permission to the user on very project in the instance. 

I infact tried that, added this user on all the permission schemes and still the issue is not resolved. 

Thanks

[Leena Bakshi]

Please see the resolution that I got for this issue