Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Cloning JBIZ Tickets without cloning the assignee or other approvers

kpuralasetty
kpuralasetty November 8, 2019

Many FNC jira ticket types are cloned to cut down on the amount of data entry. When tickets are cloned, the Assignee, Reporter, and approver/manager is inherited from the source ticket. It would be ideal if these fields were blank. Often times the users cloning can not remove the assignee of a ticket, and don't know who the ticket should be assigned to. This is creating confusion when working tickets.

Answer
Watch
Like Be the first to like this
289 views

1 answer

0 votes
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
November 9, 2019

Cloning does what it says - it makes a near identical clone of an issue.  The whole point of cloning is that it takes assignee, reporter, manager and all the other fields.

I would very strongly recommend that if you want a copy of an issue with different fields, create a new one and put the right data on it.  Stop using clone.

Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events