Does issue.epic.summary work for Tasks in Team Managed Software Projects?

[Rasneet Kanwar]

Hi, we've set up automation to copy Epic Summary into a custom text field "EN". The rule is working fine for the Company Managed projects but is returning "None" for the Team Manged Project for the Task type of Issues.... Here's what we are using:

1. When: Issue Created

2. If matches: Issue Type equals Subtask

2.1 Then: Edit issue fields - Set EN as {{issue.parent.epic.summary}} ---- Works fine on Company and Team Managed Projects.

3. Else - If matches: Issue Type is one of : Task, Bug, Story

3.1 Then: Edit issue fields - Set EN as {{issue.epic.summary}} ----- Works fine on Company Managed Projects but returns "None" for Team Managed Projects.

I have also tried to use parent instead of epic but that also returns "None". Please advise.

[Petter Gonçalves]

Hello Amit,

You are correct. Once you change the resolution to the correct value, the resolved date will reflect the date you changed the resolution and not when you changed it to the final status of the issue.

That being said, you can correct this information by importing the correct value to the resolved date field using CSV Import, but it will require a lot of work depending on how many issues you configured with the wrong resolution and I'm not sure on how it will behave with the reports, although I think it's worth trying.

If you need more information on how you can import the values using CSV, please refer to the documentation below:

- Importing data from CSV