Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Livesearch set to filter to date range or exclude label?

Kimberly Onnen
Contributor
July 24, 2018

I'm on the Cloud version. I've added Livesearch to the left navigation bar and it is set to search only in a specific Space. What I would like to do is either set up a date range limit (or nothing after a certain date) or I want to be able to exclude a specific label.

I'm using Atlassian for our online help (converted from RoboHelp). I want to be able to add new content for a future release but prevent our users from seeing this information until the product is released. Is there a way to do this?

I'd prefer not to "comment out" certain sections because that's probably where competitors would be looking. While I'm good with HTML, I'd prefer to not have to add code, unless I have to.

I tried adding null or EMPTY to the label field in the Livesearch settings, but that didn't work. I also tried -test. I was hoping that meant it would search everywhere else BUT in items with that label.

My other option, I guess would be to label all of the current stuff with "Current" and maybe "New" for the new stuff. Then again, the New label would still show under labels, correct? (Or is there a super secret way to hide a label from showing?) 

 

Thanks!!!

1 answer

0 votes
Zak Laughton
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 27, 2018

Hi Kimberly,

I understand you have a public space for customers, and you'd like to prevent users from seeing certain content until its release date. I do not recommend going about this by excluding it from a search. Even if it can't be found with the Livesearch macro, it could be found with the site search, page tree, a different Livesearch macro, URL guessing, or a number of other methods.

Instead I recommend restricting view access to the pages with one of the following methods:

  • Set page restrictions on the pages, allowing view access only for those who should see it. On the day of release, remove the view restrictions.
  • Create a private space to create the content, then move it into the public space when it is released.

Both options above will limit who can view the pages or find them in search results, and guarantee users won't be able to access the pages through other methods. You may also want to make a user group of the people who can view these pages before they're released so they can easily be applied to all permissions and restrictions.

Related docs:

I hope this helps!
-Zak

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events