Advanced Roadmaps have missing strikethrough for resolved child issues in the Child issues panel

XMLWordPrintable

    • 1

      Issue Summary

      Strikethrough for resolved child issues:
      In the issue view of a parent issue, child issues linked via the Parent Link field are not displayed with strikethrough once they are resolved. The resolution field is set correctly – the classic panels (subtasks, issue links) do show the strikethrough for the same issues, only the Advanced Roadmaps child issues panel does not.
      If I understand correctly, the missing strikethrough for resolved child issues in the Child issues panel is expected behaviour in Jira Data Center and not something we can influence through configuration. 

      Steps to Reproduce

      1. Configure Hierarchy: Ensure you have a hierarchy level above Epic (e.g., "Initiative") configured in Administration > Applications > Advanced Roadmaps > Hierarchy configuration.
      2. Create Issues:
        • Create an Initiative (Parent).
        • Create an Epic (Child) and link it to the Initiative using the Parent Link field.
      3. Resolve the Child:
        • Open the Epic.
        • Transition it to a "Done" status. Crucial: Ensure the Resolution field is set (e.g., to "Done" or "Fixed").
      4. Verify the Parent View:
        • Go to the Initiative issue view.
        • Locate the Child issues panel (this is the Advanced Roadmaps panel).
        • Observation: The Epic's key and summary will appear normally (no strikethrough), even though it is resolved.
      5. Comparison (Sub-tasks):
        • Create a Sub-task under any issue and resolve it.
        • View the parent issue's Sub-tasks panel.
        • Observation: The sub-task key will have a strikethrough, highlighting the inconsistency.

      Expected Results

      The Epic's key and summary should appear with a strikethrough

      Actual Results

      The Epic's key and summary will appear normally (no strikethrough), even though it is resolved.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Unassigned
              Reporter:
              Meenakshi Jha
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: