I Hate Jira Because ...
-
@Bulb said in I Hate Jira Because ...:
So it's all running in the cloud either way.
Hm. Do you think people can differentiate between "public cloud" and "private cloud"?
Hardly anyone would call the latter a "cloud", but rather their "IT department".
-
@Bulb said in I Hate Jira Because ...:
a mixture of English and our native language
Czenglish?
Czingle bells, czingle bells, czingle...
-
@BernieTheBernie said in I Hate Jira Because ...:
@Bulb said in I Hate Jira Because ...:
So it's all running in the cloud either way.
Hm. Do you think people can differentiate between "public cloud" and "private cloud"?
Hardly anyone would call the latter a "cloud", but rather their "IT department".The difference between private cloud and the usual IT shit is that private cloud has slightly nicer APIs. And less fighting over trying to make every piece of software ever use the exact same versions of basic libraries.
-
@Benjamin-Hall said in I Hate Jira Because ...:
@Bulb yeah. Jira's search makes 's search look great.
Who needs search? I just keep every ticket I've ever worked on open in a browser tab.
-
@HardwareGeek said in I Hate Jira Because ...:
@Benjamin-Hall said in I Hate Jira Because ...:
@Bulb yeah. Jira's search makes 's search look great.
Who needs search? I just keep every ticket I've ever worked on open in a browser tab.
How do you find the browser tabs?
-
@dkf said in I Hate Jira Because ...:
@HardwareGeek said in I Hate Jira Because ...:
@Benjamin-Hall said in I Hate Jira Because ...:
@Bulb yeah. Jira's search makes 's search look great.
Who needs search? I just keep every ticket I've ever worked on open in a browser tab.
How do you find the browser tabs?
They're all in the same window, in the upper left corner of monitor 2.
-
@Bulb said in I Hate Jira Because ...:
Back to reasons I hate Jiraβ¦
You can't ever find a fucking thing in it.
You might not be able to find stuff in it, but I find stuff I'm looking for pretty much 100% of the time, even if what I'm looking for is not a ticket project-dash-number.
OK, yes, it helps that I know the sort of thing the teams type into the "subject" field of the tickets, but even so, a word or two usually suffices to find what I'm looking for.(1)
(1) Even if it's the promises in songs of yesterday...
-
More reasons I hate Jira: it has no fucking undo for the fucking state changes. So if you drag an item to the wrong swimlane (especially when the assignments of states to swimlanes is confusing, which is project admin's fault, but all too common), there is no sensible fix.
-
-
@Bulb There is a ticket history and a way to find the most recently updated tickets, but yes, it's overhead which could have had a solution.
-
@JBert said in I Hate Jira Because ...:
@Bulb There is a ticket history and a way to find the most recently updated tickets, but yes, it's overhead which could have had a solution.
I know there is a ticket history, but that does not allow undoing the last step and most workflows don't allow arbitrary transitions, so the ticket can't be returned to the previous point if it was moved by mistake. Sometimes it can via a very circuitous route, sometimes it can't at all (e.g. when there is a difference between new and reopened).
-
It's a workflow that does arbitrary stuff ... there might not be a way to move the status back, or it might be rights limited.
we have several status changes that actually create a task in different project, what would an undo/revert do in such case? remove the ticket? too bad: it is a trigger for an external team that actually creates a jira ticket in their jira.:xzibit_jira_in_your_jira:
-
@Luhmann Undo the trigger, of courseβ¦
Where not possible, it should probably at least make it more obvious what it's doing and ask for confirmation. If you click the workflow from the ticket details, you see the states you are changing, but with the swimlanes you don't actually see the current state.
Yeah, that's partly problem of the project adminβthe ticket that prompted me to write that rant has several βin progressβ states in its workflow, including a βreadyβ one, which I would definitely not consider to be βin progressβ. But then we don't have swimlanes for the design phase, which is the core of the poodle.
-
...stupid "friendly" time displays. JUST SHOW ME THE ACTUAL FUCKING DATE AND TIME SOMETHING HAPPENED.
Of course, lots of other stuff besides Jira does this, but I'm much more interested in time stamps for Jira (figuring out how long I've worked on something, trying to correlate application logs, etc) than for, e.g., whatever with nodebb post times.
-
@boomzilla You can hover over the friendly time and you will get a tooltip with an actual timestamp. But yes, a personal setting to turn off friendly times would be nice.
-
@JBert yeah, that's exactly what I do...ALL THE FUCKING TIME. Goddamned annoying.
-
@boomzilla Try to look whether there's a userscript for that (yeah, yeah, and asking for help etc. etc.)
-
@Bulb that's a good idea.
-
@Bulb said in I Hate Jira Because ...:
@boomzilla Try to look whether there's a userscript for that (yeah, yeah, and asking for help etc. etc.)
LOL, found several Jira tickets for Jira to support this. Apparently there's some server config that changes this but they've been pretty adamant in the face of angry customers that it would be ugly or something.
Found someone who used ChatGPT to gin up some custom styles:
.livestamp::before { content: attr(title); white-space: nowrap; } .livestamp { visibility: hidden; position: relative; min-width: 100px; height: 1.2em; line-height: 1.2em; display: inline-block } .livestamp::before { visibility: visible; position: absolute; top: 0; left: 0; line-height: 1.2em; }
That mostly works. There are a few dates that aren't changing for some reason. Including, of course, the "Updated" value, which is the one that prompted this rant.
-
@boomzilla actually, that was not right at all. Maybe a different version. This seems to do it:
.date.user-tz::before { content: attr(title); } .livestamp { visibility: hidden; }
-
@boomzilla said in I Hate Jira Because ...:
@boomzilla actually, that was not right at all. Maybe a different version. This seems to do it:
.date.user-tz::before { content: attr(title); } .livestamp { visibility: hidden; }
Well, it's close, but sometimes the fuckers put a time zoned time in a
livestamp
(e.g, when a file was attached). Urg....livestamp { - visibility: hidden; + margin-left: 0.5ex; }
-
ITT, @boomzilla discovers why it's better to just in real time
-
It's one thing to display 'friendly' dates ... but can we at least sort them correctly ...
this is ordered descending on that timer field, in what world are those 2h between 4d and 3d
Not a Jira bug but I guess we lost these SLA timings
-
@Luhmann TIL that 1 day 40 hours (so, 2 days 16 hours) was longer than 4 days 9 hours.
-
@Arantor
also day != 24h
but rather a 'working day' based on the what is configured in the jira project but yeah no idea why sometimes it gives such strange values. Here everything > 9h should be marked as 'a day'. So 4d 9 h should be 5d and 1d 40h is probably 5d 4h or something. Damn that does make 1d 40h > 4d 9h.Still Jira is shit for not displaying it right.
-
@Luhmann β¦ you don't have more than 40 hours a week, do you? But that means 1d 40h is actually at least 1w 1d, and therefore > 1w, and it's not sorted right either.
-
@Luhmann
same goes when counting up from days -> weeks. more then 5 days should in most cases give you 1w EXCEPT for when there is an official holiday/closing day defined OR the timer uses a different calendar, eg. blocking issues are not limited to trivial things like working hours.
-
@Bulb
a week should be 9h x 5d = 45h
this is 'business hours' not 'individual working hours'
-
@Luhmann But the estimated and worked fields should be just numbers. They shouldn't care when the hours were spent, so 5 days should always be called 1 week.
-
@Luhmann β¦ which field is that? I'm only used to those values in the estimates and logged time worked, and for those 1 day = 8 hours and 1 week = 5 days, because that is the normal hours worked by a full-time employee.
-
@Bulb
an SLA Timer field, but that would explain why I struggled with estimated days on the rare occasion I used those.
-
Which barbaric place are y'all living in that has work days longer than 7.5 hours anyway?
-
@Steve_The_Cynic
... would have thought that was common knowledgeOffice hours are 8h-17h30 eg 'we are open and working' that doesn't mean you work from 8h to 17h30. You have to average around 7,7 here.
-
@Luhmann Ah. OK. Yeah, for me the nominal work hours are 9h00 to 18h00, with an hour and a half for lunch, except Fridays, where the end time is 17h30. Makes a total of 37 hours per week, which is longer than normal for (35 hours per week), and to make up for it, we get 11 days of what's called "RTT" == days off above the total of five weeks we get otherwise. (Yeah, I'm showing off in front of all the ians here...)
-
@Steve_The_Cynic
pretty similar to where the mimimal work roster for a full time is 35 and maximum is 40h per week. You get additional days off depending on the regime. Above your minimal 20 days off, the hole slew of official holidays and then additional days you collect as bonus points along the way.
But let's not start about the 3 days per year you can call in sick without proof because that really start sounding like communism
-
@Steve_The_Cynic said in I Hate Jira Because ...:
(Yeah, I'm showing off in front of all the ians here...)
-
@Steve_The_Cynic said in I Hate Jira Because ...:
@Luhmann Ah. OK. Yeah, for me the nominal work hours are 9h00 to 18h00, with an hour and a half for lunch, except Fridays, where the end time is 17h30. Makes a total of 37 hours per week, which is longer than normal for (35 hours per week), and to make up for it, we get 11 days of what's called "RTT" == days off above the total of five weeks we get otherwise. (Yeah, I'm showing off in front of all the ians here...)
But the price is living in France? For a half hour per day less WTDWTF? IDGI
-
@boomzilla Your xenophobia is showing ...
More seriously, I like France anyway, so that's just icing on the cake.
@Luhmann said in I Hate Jira Because ...:
But let's not start about the 3 days per year you can call in sick without proof because that really start sounding like communism
Huh. doesn't offer that. All sick days must be justified one way or another, but on the other hand, it's possible to get a justification, and therefore a sick day, for a day where you have a big series of medical tests and can't go to work that day.
-
@Steve_The_Cynic said in I Hate Jira Because ...:
@boomzilla Your xenophobia is showing ...
Well, I am a barbarian, after all.
-
@boomzilla Not sure... you look more like a cleric/monk multiclass.
-
@Applied-Mediocrity yeah but I have standard 8 hour work days.
-
@boomzilla
Damn capitalism
-
@HardwareGeek Sounds like it should just log you out. My work currently uses ADO with Okta SSO and I'm either on the page or it's demanding I login.
We're moving over to JIRA though, so I'll definitely be raising
helltickets with ops about this when I'm done with trying to get a git push/pull to work on our internal gateway.
-
@Shoreline said in I Hate Jira Because ...:
Okta SSO
The same Okta that had the slight total security pwnage incident recently?
-
@dkf said in I Hate Jira Because ...:
@Shoreline said in I Hate Jira Because ...:
Okta SSO
The same Okta that had the slight total security pwnage incident recently?
They've totally fixed it for real this time.
-
-
@boomzilla said in I Hate Jira Because ...:
...stupid "friendly" time displays. JUST SHOW ME THE ACTUAL FUCKING DATE AND TIME SOMETHING HAPPENED.
Of course, lots of other stuff besides Jira does this, but I'm much more interested in time stamps for Jira (figuring out how long I've worked on something, trying to correlate application logs, etc) than for, e.g., whatever with nodebb post times.
The newest Jira version in the cloud apparently allows you to not only hover over a friendly time to get a tooltip with a timestamp, it also allows you to click it. At that point all friendly times turn into full timestamps for me. It even seems to survive a refresh of the page.
Filed under: Insert Discoverability Blakeyrant
-
When someone's account is deactivated, their name in tickets gets changed to "Former user". Good luck trying to follow the conversation
-
@homoBalkanus I believe that's only the case for completely deleted users, unless it's now done automatically for GDPR reasons.
In the past, merely deactivating a user account would have them show up as
Firstname Name (Unlicensed)
.
-
@JBert
There is a '[X] (Inactive)' suffix here