[#JRA-1578] Search facility should be able to search on "COMPONENT" or "VERSION" and search "COMMENTS" and "CHANGE HISTORY"

JIRA

Search facility should be able to search on "COMPONENT" or "VERSION" and search "COMMENTS" and "CHANGE HISTORY"

Created: 15/Apr/03 11:52 PM Updated: 20/Dec/04 10:34 PM

Component/s:

Filtering & Indexing

Affects Version/s:

2.1 Enterprise

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue duplicates:

JRA-5536 Search the change history

Participants:	GUY WILLIAMSON, Jeff Turner [Atlassian], Kevin James, Mike Cannon-Brookes [Atlassian] and Milo van der Linden
Since last comment:	177 weeks, 2 days ago
Resolution Date:	20/Dec/04 10:34 PM
Labels:

Description

« Hide

The search mechanism could be improved greatly by adding these features. We have alot of projects with common "COMPONENTS" and "VERSIONS" and need to be able to include these in 1 search.
Also we have found when you MOVE a task from one project to another the only history you get (like previous task #) is contained in the "CHANGE HISTORY" This (and COMMENTS) cannot be searched

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Mike Cannon-Brookes [Atlassian] - 07/May/03 09:01 PM

Guy,

I'm not quite sure I know what you mean. Could you elaborate?

You can already search on comments?

Searching on change history is much more complex, we might add this in a future version.

What do you mean by searching on components / versions?

Cheers,
Mike

[ Permlink | « Hide ]

Milo van der Linden - 29/Jul/03 09:23 AM

We also have an urgent need to search on the change history, why?

We work with an external support contractor that wants to have a weekly report on the issues that where once assigned to his company and have been reassigned to someone of our company.

[ Permlink | « Hide ]

Kevin James - 13/Dec/04 04:16 PM

I don't know if this is what Guy is alluding to, but we have an important need to filter across multiple projects, not All projects, but multiple projects. We have several projects that are released as standalone products. However, they are also bundled up and shipped as a bundled product or suite. Now we may be working on Suite 4.0 which consists of ProjectA v4.5, ProjectB v8.1.1 and ProjectC v7.3. We want to create a filter that would filter across the specific Fix For versions of these three products. Then we could call the filter Suite 4.0 and it would give us the stats we need. This capability would even be more valuable now that you have portlets that can give you stats based on a filter.

Right now we have a custom field called Bundled products that we use to generate this kind of filter, but users are always forgetting to set the either the Bundled Products field or the Fix For version or the choose the wrong Fix For version to go along with the selected Bundled Products. It just not an ideal solution.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 20/Dec/04 10:34 PM

This issue seems a bit unfocused, so please see instead:

Search the change history:

http://jira.atlassian.com/browse/JRA-5536

Search multiple projects:

http://jira.atlassian.com/browse/JRA-2755