Don, if only it were so! Not only can't you give it an alias, you also can't use the '(All)' in a field calculation, which would also be handy. If you write these up in the Idea section I'll give it a +1.

--Shawn

You could use a parameter instead and use a calculated field to apply the desired filter.

please provide a sample workbook if you would like to see an example.

Can you please attach as a packaged workbook, .twbx? (no data is included in a a .twb file)

How about the attached?

You can get fancier with checking the Month vs the month for TODAY() as well.

Joe, that works fine as long as you don't need to select multiple months. This is why we need to be able to give the (all) in a filter an alias. (But then you know that already.)

You are describing a different situation, and it has a different solution.

For this thread start, the question was to alias a single select quick filter on data that does not change, and one solution is to use a parameter. Waiting for Tableau to add the ability to alias the (All) option is another route, but does not help anyone today

If the data changes or you need a multi-select, then another possible solution (within the current constraints of Tableau), is to duplicate the data.

Take a look at the attached, be aware it does not make sense to select a"Total YTD" and the other months at the same time.

Are you noticing a pattern? If you have the ability to transform your data prior to Tableau (using custom SQL falls into this category, so does ETL), you can accomplish almost anything in Tableau.

Joe interesting solution, as usual. But I'll stick with the feature request Don posted in the Ideas section.

You and I look at these forums a bit differently, I think. A lot of the Tableau folks obviously monitor these forums, looking for feedback, and even ideas on ways to improve their product (I assume). While I'm happy to answer questions when I can, and provide work-a-rounds (in many cases things you taught me), ultimately I use these answers as ways of pointing out some of the places Tableau could make things better/easier, in the hope that someone is listening.

I guess it comes down to you are primarily trying to help someone today; I'm trying to help us all tomorrow. I really don't know that Tableau survives if it stays a 'programmer' driven tool where it takes a custom SQL join just to change the name of a filter option. I hope I'm wrong, I really enjoy working in this software. Anyway...

--Shawn