Just recreating the request that was deleted on the forum upgrade. Putting the year in messages would be very useful for projects that don’t quite fit within 1 calendar year (or several for that matter).

-Eric

To me this seems more like an imposed philosophical constraint as opposed to a technical one. i.e. a project shouldn’t span years.

Confirmation Jason?

-Eric

We have many projects that span years. We have not been on Basecamp long enough for us to have projects on there that have lasted for several years, but we certainly will. Most of our projects can go on for two or three years. We have even had some go as long as ten years.

I stopped using basecamp because of this very reason. Ugh.

-Eric

Definitely agree that this would be useful. A nice compromise would be to only display years on messages that are not in the current year.

We had an issue today where we were trying to figure out whether a particular message was posted in 2006 or 2007. The only way we could figure it out was by looking at a calendar and using the day of the week to determine the year.

Agreed, we most definitely have projects that span years. Basecamp is used in all different industries – who’s to say if a project can, or can’t span years? We have been using basecamp for 3 years & have an ongoing project that we’ve been using since day 1 with basecamp. I need to go into archived messages & then count how many June’s ago the message was to see when it was posted. Seems so simple – we need the year!!

As Basecamp gets older (me included…) we need this also.
We use Basecamp also as a knowlede: base.
However our projectname system includes the year to find back a project.
So if you want to have an immedialty solution:

“LAM07-022 StorEvolution new store concept ”: first three letters are the client, then the year, next the project number in that year, the name of the project.

I ran into this today.

I ended up wasting 20 minutes trying to figure out what year a list of February results came from.

Basecamp getting older definitely needs years attached to the message (at least the main one, if not the comments; context should be enough). At the very least the year should be hidden in comments (so I can look it up in source when it’s important).

Years in dates is not optional. This is basic functionality.

+1

The perma page for a message now includes the year it was posted.

A much appreciated addition, thanks.

• add the year to the message list view, as well as the All Messages view (add the year to the month headings)
• add date (including year) to messages returned by Search

Thanks much!

Our organization desperately needs this also. Our projects DO span years. It is not enough just to have it on the “perma page”, it should show up in lists also.

Thanks!