Issue Details (XML | Word | Printable)

Key: JRA-2182
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Greg Perrott
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
JIRA

Filter Subscription does not run as correct user

Created: 17/Aug/03 08:15 PM   Updated: 03/Sep/08 09:49 PM
Component/s: Filtering & Indexing
Affects Version/s: 2.3 Enterprise
Fix Version/s: 3.13.x

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Greg Perrott, Jed Wesley-Smith [Atlassian] and Scott Farquhar [Atlassian]
Since last comment: 44 weeks, 3 days ago
Labels:


 Description  « Hide
I created a Filter to show the overdue issues for the current user and shared this with the developers group.

This worked fine in that every developer was able to use the filter to see their overdue issues.

I then thought it would be nice to email this to all the developers prior to our weekly meeting so I setup a subscription for the filter and subscribed the developers group. Instead of each developer receiving their overdue issues, they all received an email with a list of my overdue issues.

Had I wanted to send a list of my overdue issues to the group, I would have used my user id in the Filter rather than current user.

I guess the work around would be to get each deveop to subscribe individually to the filter and then I assume it would work although I haven't tested this theory.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] added a comment - 17/Aug/03 08:38 PM
Yes - this is a difference to the behaviour that is expected.

I'll try and get this fixed up.


Scott Farquhar [Atlassian] added a comment - 09/Nov/03 07:58 PM
Updated summary to better reflect the problem

Jed Wesley-Smith [Atlassian] added a comment - 06/Dec/07 08:00 PM
The fix for this issue has not been able to make it into JIRA v3.12. We are hoping to incorporate it into v3.12.1. As of writing however, there are 163 items scheduled as Fix For v3.12.1. We will not be able to include all of them.