Bug 849539

Summary:	Allocating tags to different projects doesn't influence search results
Product:	[Community] PressGang CCMS	Reporter:	Dana Mison <dmison>
Component:	Web-UI	Assignee:	pressgang-ccms-dev
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	lnewson, mcaspers, topic-tool-list
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-04 05:20:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dana Mison 2012-08-20 07:08:35 UTC

Tags can be allocated to projects.  This doesn't seem to do anything except separate them into different tabs on the search screen.  It doesn't appear to affect the search results.


Expected behaviour:
When searching, if I select a tag from only one of the project tabs that it appears under: I expect that only the topics tagged with that tag from the project  will get matched by the search.

Actual behaviour:
The search matches all the topics with that tag regardless of the project.

Comment 1 Lee Newson 2012-08-20 08:38:08 UTC

A project isn't mapped to any topics therefore this isn't possible atm. Projects are really just a grouping of tags that make it more user friendly. To do this I imagine you would need to have a "Project" category tag type of setup.

Anyways that's the reason it doesn't work, but I'll leave it for Matt to comment/have a look and then work from there.

Comment 2 Dana Mison 2012-08-21 02:53:05 UTC

Re: conversation in meeting

1. The way this works should be considered correct for this version and documented as such to avoid potential confusion (create a doc bug for this?)

2. The way this works should be made more intuitive in the new UI

3. Should this bug become an RFE for 2.x ?

Comment 3 Matthew Casperson 2013-02-04 05:20:42 UTC

This is the expected behaviour. This is a training/documentation issue.