epic add regression for next-gen projects: unconditional SkipNotify: true breaks non-admin users

[jmdaly]

Hi there, thanks for the great tool! I noticed an issue related to adding issues to epics when the user is not an admin user.

Describe the bug

jira epic add does not seem to work for users who don't have Jira admin (or project admin) permissions on next-gen (team-managed) projects. The command fails with:

   SOME REQUESTS REPORTED ERROR:
     - ISSUE-123: To discard the user notification either admin or project admin permissions are required.

The request fails entirely. No issues are added.

Please provide following details

1. JiraCLI Version:

(Version="1.7.0", GitCommit="Homebrew", CommitDate="2025-08-30T08:30:25+00:00", GoVersion="go1.25.5", Compiler="gc", Platform="linux/arm64")

2. Are you using Jira cloud or on-premise jira server?

SERVER INFO
-----------

Version:         1001.0.0-SNAPSHOT
Build Number:    100290
Deployment Type: Cloud
Default Locale:  en_US

3. What operating system are you using? Also mention version.

Ubuntu 24.04

4. What terminal are you using? Also mention version.

WezTerm 20240203-110809-5046fc22

To Reproduce

Steps to reproduce

1. Configure jira-cli with a next-gen project (project.type: next-gen in config)
2. Run jira epic add EPIC-KEY ISSUE-KEY as a non-admin user
3. Observe the error above - no issues are added to the epic

Expected behavior

Issues are added to the epic (parent set), watchers receive a notification email as normal.

Screenshots

Additional context

It looks like this is a regression introduced in #855. That PR added a --skip-notify flag to jira issue edit, and as part of the change also set SkipNotify: true unconditionally in the next-gen path of epic add (and epic remove)