-
Suggestion
-
Resolution: Unresolved
-
1
-
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
Confluence should allow uses to create and save "smart lists": a list of Confluence content retrieved by applying a configurable set of search criteria.
For example, a smart list might be created with the following search criteria:
- content type: page
- label: documentation
- spaces: favourite spaces
- created by: Charles Miller
This list of content should be able to be saved as a "smart list" then shown on the dashboard, subscribed to as RSS, notified of changes via email, etc.
The search criteria should be extensible through plugins, so custom criteria for plugins such as the metadata plugin can be defined.
This functionality is similar to JIRA's filters, but we can probably improve the UI in some ways.
- incorporates
-
- Closed
-
- Closed
-
- Closed
-
- Gathering Interest
- is duplicated by
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
- relates to
-
- Gathering Interest
[AI-771] Smart lists (persistent search filters)
The "News Watching" features are something that I've been looking for for a long time. Email is still the way that most people get notifications in our corporation. Having this functionality in Confluence would significantly increase the adoption rate and the usage of the news features.
Marc Bailey
added a comment - This would rock - especially if applied across Jira and Confluence. (Imagine a content type of Jira issue in search).
We constantly have to set up filtered feeds and searches for news in particular projects using tags, and maintain the same tags across Jira and Confluence (and our own product).
BTW - please don't feed the animal. Recruiters don't need to be any more keyword driven than they already are.
Marc Bailey
added a comment - This would rock - especially if applied across Jira and Confluence. (Imagine a content type of Jira issue in search).
We constantly have to set up filtered feeds and searches for news in particular projects using tags, and maintain the same tags across Jira and Confluence (and our own product).
BTW - please don't feed the animal. Recruiters don't need to be any more keyword driven than they already are.
Nikki Stokes
added a comment - Maybe this feature could include the ability to display a user's recent searches, along the lines of a user's favourite pages, or the recently updated pages list.
We rely quite hevaily on searching to find particular pages in our wiki, and there are certain searches we do over and over. It would be very useful to be able to display a list of recent searches and click on one of them to run it again.
Nikki Stokes
added a comment - Maybe this feature could include the ability to display a user's recent searches, along the lines of a user's favourite pages, or the recently updated pages list.
We rely quite hevaily on searching to find particular pages in our wiki, and there are certain searches we do over and over. It would be very useful to be able to display a list of recent searches and click on one of them to run it again. Pasting Soren's suggestion:
==========snip=============
This is a "how-to" question on how we can use Confluence better in the Atlassian recruitment process with our recruiter. I pinged Sam on the Confluence dev team, but he suggested I open a support ticket.
I'd like to find the best way to create a continuous watch for incoming content.
The use-case is
1. Use sets a "watch" where the criteria for the watch is a set of key word which appear in a resume - the resume is not tagged.
2. A resume comes into the system
3. The user's watch directs them to matching resumes - it doesn't really mater how but the user should be directed to new content. They should be presented results they have already seen.
What is the best way to accomplish this? I guess I'm imaging some sort of RSS feed on a lucene query.
==========snip=============
We could extend this to allow a user to save search terms as well.
Cheers,
Dave
For an example of what we're considering, see Charles's work on the last Atlassian ShipIt day:
http://blogs.atlassian.com/2006/06/shipi_day_3_part_1_confluence/
I posted a long comment that actually belongs in this issue, but it was in response to another user's comment in another issue. So I'll just link to it from here.