-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Problem Definition
On Jira Service Management (former Jira Service Desk), comments in issues are either public or internal – see Editing and collaborating on issues for further details.
If an issue from a Service Management Project needs to be moved to a project of a different type, such as Software or Business, then all comments in that issue are made public, including internal comments which may not be ideal.
Suggested Solution
It would be nice to have an option on the Move Issue wizard to associate internal comments to a role in the target project, keeping these comments restricted.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- links to
[JSDSERVER-7119] As a user I want to be able to restrict internal comments to a Project role when moving an issue from a Jira Service Management Project to a different Software or Business Project
| Support reference count | New: 1 |
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 535713 ] |
| Labels | New: ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 976921 ] |
| Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 535713 ] |
| Description |
Original:
h3. Problem Definition
On Jira Service Management (former Jira Service Desk), comments in issues are either public or internal -- see [Editing and collaborating on issues|https://confluence.atlassian.com/servicemanagementserver/editing-and-collaborating-on-issues-939937207.html] for further details. If an issue from a Service Management Project needs to be moved to a different project type, such as Software or Business, then all comments in that issue are made public, which may not be ideal. h3. Suggested Solution It would be nice to have an option on the [Move Issue wizard|https://confluence.atlassian.com/servicemanagementserver/moving-an-issue-939937218.html] to associate internal comments to a role in the target project, keeping these comments restricted. h3. Workaround _Currently there is no known workaround for this behavior. A workaround will be added here when available_ |
New:
h3. Problem Definition
On Jira Service Management (former Jira Service Desk), comments in issues are either public or internal -- see [Editing and collaborating on issues|https://confluence.atlassian.com/servicemanagementserver/editing-and-collaborating-on-issues-939937207.html] for further details. If an issue from a Service Management Project needs to be moved to a project of a different type, such as Software or Business, then all comments in that issue are made public, including internal comments which may not be ideal. h3. Suggested Solution It would be nice to have an option on the [Move Issue wizard|https://confluence.atlassian.com/servicemanagementserver/moving-an-issue-939937218.html] to associate internal comments to a role in the target project, keeping these comments restricted. h3. Workaround _Currently there is no known workaround for this behavior. A workaround will be added here when available_ |