Issue Details (XML | Word | Printable)

Key: JRA-2682
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Dmitry Kashin
Votes: 8
Watchers: 2
Operations

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

Add ability to watch components or to filter by components

Created: 15/Nov/03 07:26 AM   Updated: 10/Sep/08 08:45 AM
Component/s: Filtering & Indexing
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: adam baker, Andre Nachtigall Tessmann, Dmitry Kashin, Owen Fellows, Sajjad Zaidi and Todd Gross
Since last comment: 3 weeks, 6 days ago
Labels:


 Description  « Hide
For people translating JIRA is very interesting to know all changes made in i18n component.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Owen Fellows added a comment - 16/Nov/03 08:00 PM
It is already possible to filter by component.

Search under the JIRA project then the list of Version and Components appear.

Is this what you mean, or have I miss read the Issue.


Dmitry Kashin added a comment - 17/Nov/03 02:33 AM
Personally I can search only by project, not by component. The solution is to give us this permission, and we could subscribe to filter by target component.

adam baker added a comment - 01/Jun/07 11:16 AM
I agree, the inability to filter on component AT THE SAME TIME as other fields is extremely annoying and reduces productivity.

Todd Gross added a comment - 03/Jun/08 12:01 PM
Having the option to create a filter using component is vital for how we desire to manage our projects.

Sajjad Zaidi added a comment - 30/Jul/08 08:42 PM
We really need this capability:
Ability for any user to subscribe to issues on a per component basis. i.e. any time an issue gets filed against a certain component, the person who has
subscribed to that component automatically gets an email on the issue.

This seems to be a severe limitation of the tool, and is already causing issues within our team wrt issue duplication (people not knowing that a certain issue has already been filed/resolved on a certain component and therefore filing it again).


Andre Nachtigall Tessmann added a comment - 10/Sep/08 08:45 AM
This feature is essential. Please implement it as soon as possible. It`s really annoying. As Saijjad said, "Ability for any user to subscribe to issues on a per component basis. i.e. any time an issue gets filed against a certain component, the person who has
subscribed to that component automatically gets an email on the issue. ". Also very very important for our internal process.