Issue Summary

This is reproducible on Data Center: Yes

There's inconsistent behavior in issue editing tied to the "Link Issues" permission in the parent project. Users with "Browse Projects" and "Link Issues" permissions in the parent project can edit child issues via both the "Edit" menu and the issue page (inline editing). When the "Link Issues" permission is removed from the parent project, users can still edit the issue inline on the issue page (for specific fields), but the "Edit" option displays a dialog form with all the visible fields that won't allow editing showing the message "Error while validating parent link: You do not have permission to link issues in this project".

Steps to Reproduce

1. Create two projects: "Parent" (e.g., SCRUM1) and "Child" (e.g., SCRUM2).
2. Add a new issue type (e.g., "Initiative").
3. Configure a new hierarchy level above "Epic" in Advanced Roadmaps and associate it with the "Initiative" issue type.
4. Create a user, User01, with the following permissions:
   • Child Project (SCRUM2): "Browse Projects" and "Link Issues" permissions initially.
   • Parent Project (SCRUM1): All permissions (includes "Edit Issues").
5. Log in as User01 and create an Initiative in SCRUM1.
6. Log in as a different user (e.g., User02) with all permissions on SCRUM2 and create an Epic in SCRUM2.
7. Link it to the Initiative in SCRUM1 using the "Parent Link" field or Advanced Roadmaps.
8. Verify that User02 can edit the Epic via:
   • The "Edit" menu (e.g., the pencil icon or "Edit" button in the UI).
   • Inline editing on the issue page.
9. Remove User02 "Link Issues" permission in SCRUM1, leaving only "Browse Projects" permission in SCRUM1 and all permissions in SCRUM2.
10. Attempt to edit the Epic again as User02 via:
    • Inline editing on the issue page (e.g., updating fields like Summary or Description).
    • The "Edit" menu (opening the full edit dialog).

Expected Results

• User02 should be able to edit the Epic in SCRUM2 via both the "Edit" dialog form and inline on the issue page, regardless of the "Link Issues" permission in SCRUM1, since edit permissions are granted in SCRUM2 where the Epic resides.
• The "Link Issues" permission in SCRUM1 should only govern linking actions (e.g., adding or modifying the "Parent Link"), not the ability to edit other fields in the Epic via the "Edit" menu.
• If the "Parent Link" field is unchanged in the edit dialog, it should not trigger a permission check that blocks the entire update.

Actual Results

• With "Browse Projects" and "Link Issues" permissions in SCRUM1:
  • User02 can edit the Epic via both the "Edit" menu (full dialog) and inline on the issue page.
• After removing "Link Issues" permission from SCRUM1 (leaving only "Browse Projects"):
  • User01 can edit specific fields (e.g., Summary, Description) inline on the issue page without issue, as this does not involve the "Parent Link" field or linking permissions.
  • User01 cannot use the "Edit" menu; the dialog form opens, and the fields are editable, but any attempt to save the changes will result in the message "You do not have permission to link issues in this project" even if the parent link was not touched.
• User01 cannot re-add the "Parent Link" to the issue in SCRUM2 due to the missing "Link Issues" permission on SCRUM1, which is consistent with permission settings.

Workaround

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