[#JRA-1907] Ability to add watchers/notifications to a single issue (Issue roles)

JIRA

Ability to add watchers/notifications to a single issue (Issue roles)

Created: 06/Jul/03 10:22 PM Updated: 23/Jun/06 02:07 PM

Component/s:

Events / Listeners

Affects Version/s:

2.2 Pro

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue duplicates:

~~JRA-716~~ Add other users to watch

This issue is duplicated by:

JRA-2322 transferring all issues reported by a user to another user

~~JRA-2458~~ find issues commented by a given user

~~JRA-652~~ Allow user or admin to add watches for others on an issue

~~JRA-2775~~ Add external watch (E-mail address) on issues

~~JRA-1606~~ Abillity to assign more than one user

~~JRA-1912~~ Alility to assign a task to more than 1 developer

~~JRA-4210~~ Add people to the watch list

Part

This issue incorporates:

JRA-2106 Ability to forward issues to other users

JRA-2460 Ability to watch all linked items

Reference

This issue is related to:

JRA-1397 Assign issues to multiple users or a group

JRA-2665 Customising filter views

~~JRA-1532~~ Ability to Create New Issue - but Reported by another user

JRA-1187 Need to filter by 'commenter'

JRA-2468 allow filter on issues "worked on by"

JRA-2634 Allow multiple groups to view comments

JRA-261 Improve watching functionality

JRA-2167 CC email address list in issues (notify arbitrary emails)

~~JRA-1829~~ notifications sent to value of custom field

~~JRA-2611~~ Assign a task to a user OR A GROUP

Participants:	Andy Ciordia, Anton Mazkovoi [Atlassian], Dave Loeng [Atlassian], Grigori Karlik, Jag Gill and Owen Fellows
Since last comment:	108 weeks, 2 days ago
Labels:

Description

« Hide

I would like to be able to add a watcher/person to be notified of changes in issue but which is external to our organization.
I don't want him to see everything what is happening on a project (that's what notification schemes are for) and I don't want to create him as an user in our Jira (to make him a regular watcher).
I only want him to be notified over e-mail when issue is resolved, for instance.
I imagine that to be done by entering his e-mail to an additional issue field.

– Damjan Perenic

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Owen Fellows - 09/Nov/03 08:36 PM

We need to make it possible to assign issue level security to comments.

[ Permlink | « Hide ]

Owen Fellows - 10/Nov/03 12:29 AM

If we add roles for watches, voters etc. We can do the same for commenters and lots of other things.

[ Permlink | « Hide ]

Owen Fellows - 10/Nov/03 12:31 AM

Linking issue to user throw roles could include user that have commented on an Issue.

[ Permlink | « Hide ]

Owen Fellows - 10/Nov/03 07:59 PM

Could do this a part of the Role feature but does with complex issue linking may cause a large number of Issue to be watched.

[ Permlink | « Hide ]

Andy Ciordia - 12/Aug/04 02:51 PM

Apologies for being blind. This issue is already being discussed by you all it seems.

[ Permlink | « Hide ]

Grigori Karlik - 28/Sep/04 04:24 AM

How is the status of this bulk of features?
Especially I am interested in the parallel workflow-function / two assignees per issue.
Is this functionality released in the new Jira 3.0 version?

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 28/Sep/04 08:43 PM

In JIRA 3.0 it is possible to view and edit the watchers list of an issue.

Unfortunately we did not get enough time to implement multiple assignees for JIRA 3.0.

[ Permlink | « Hide ]

Jag Gill - 23/Jun/06 02:07 PM

I'm interested in in how parallel assignment would be necessary.

If more than one person is working on an issue, cannot the deliverables be broken down into sub-tasks assigned to each developer (or other role)? In all the situations that I can think of, if there is more than one person working on an issue, they are never doing the same work, but may have responsibility for a workstream that contributes towards the resolution of the issue. Even when there may be multiple testers involved, they normally have designated functionality areas to test that don't strictly overlap. This way it is also easier to track where (or who) the blockages for an issue's resolution are and take appropriate remedial action.

I realise that this may result in a large number of sub-tasks (which currently can't then be further sub-tasked - though I would argue that this is more important than multiple assignees), so perhaps a further workaround is to have a lead assignee, who has overall responsibility for delivering the work, and specify additional contributors to that workstream through a multi-user picker?