I discovered this bug today as well. I found that it only happens when the minutes are divisible by 5. If I enter any other number for the minutes, it works correctly. Maybe the code is trying to be helpful by showing the friendly text if the cron expression looks like "hourly," but instead of checking whether the minutes are 0, it instead checks whether the number is divisible by 5? 

Any plans to fix this?

lestin No one said we are not going to react on it. All I did is I ranked this issue according to it's true severity, which is "minor loss of functionality". As for proof of it being display issue: it's one click away: configure cron expression, save it, then go back to cron editor to see it's there. Then wait for build to be triggered at specified time.

There's nowhere says the setting means "not the time of trigger but the range of hours". What's the point of having a minute field then? means range of minutes it's applicable?

I'm not sure I follow. This is how the UI looks like:

We have "Interval" which is "every hour" without minute part. The only minute fields are in "from" and "to" controls which lets you to tell for example from " 9:00 a.m to 5:00 p.m, every hour"

If so, can we request an option of "hourly every minute" then? I dont mind the range of seconds when it kicks the job off ...

The most flexible way of configuring schedules is to edit cron expression directly.

I'm surprised to pick up the Atlassian's support on this case, for all your paid customers!

1. I don't think "just a display issue" justifies the reason not to react on it and, there's no proof showing it's "just a display issue" — i didn't bother to very that myself, oops!
2. If "Daily every hour" means it is round clock, then the whole UK bus system is wrong as it uses "05 every hour" to tell people that the bus arrives at 9:05 for example.
3. There's nowhere says the setting means "not the time of trigger but the range of hours". What's the point of having a minute field then? means range of minutes it's applicable?
If so, can we request an option of "hourly every minute" then? I dont mind the range of seconds when it kicks the job off ...

Thanks & sorry about the rant.
Lestin

bob.swift@charter.net I'm ranking this issue down, as it's just a display issue: if you switch to cron view, the expression is there and more importantly, scheduling works as expected (according to cron).

" Daily selected, every hour, and the time is 00 (not 55)" -> Actually it's "Daily every hour" which is confusing but technically correct. The time shown is not the time of trigger but the range of hours when it's applicable, which is, again, correctly set to 12a.m - 12 a.m (whole day).

Also applies to Scheduled "Repository polling" trigger.