Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Maybe I could get better bug reports from clients if I made them use this.
I wonder if it has Jira integration.
5 -
I prefer silent kills.
× open Jira ticket classified as a BUG REPORT
× Title: "Mike"
× Description: "Mike is working with us"
× assign it to Mike
× reopen it every time it's closed6 -
How to get your Jira ticket resolved:
1: Assign in it the person
2: Mention him on the ticket
3: Remember the ticket number
4: Sneak into his office
5: 
10 -
This project manager, man....
> Sends email to a client "Dear Ms X, here's your password for the Jira board: [...] Please handle it with care and keep it secret."
> Email goes out to 5 people.
6 -
boss: please look into tools that do X.
fullstackchris: Ah, here's a solution we can use!
boss: I don't want to use it because it is too complicated.
fullstackchris: ok, that's fine with me...
[one week later] boss: oh I found this nice site that does X, can we do X?
fullstackchris: YES, THAT'S EXACTLY THE SOLUTION I ALREADY FOUND, *AFTER* YOU ASKED ME TO LOOK FOR A SOLUTION, AND IN THE END YOU DIDN'T WANT TO DO IT. OH HAVE YOU CHANGED YOUR MIND?!?!
F*@#! *%*#8 -
Welcome back to practiseSafeHex's new life as a manager.
Episode 2: Why automate when you can spend all day doing it by hand
This is a particularly special episode for me, as these problems are taking up so much of my time with non-sensical bullshit, that i'm delayed with everything else. Some badly require tooling or new products. Some are just unnecessary processes or annoyances that should not need to be handled by another human. So lets jump right in, in no particular order:
- Jira ... nuff said? not quite because somehow some blue moon, planets aligning, act of god style set of circumstances lined up to allow this team to somehow make Jira worse. On one hand we have a gigantic Jira project containing 7 separate sub teams, a million different labels / epics and 4.2 million possible assignees, all making sure the loading page takes as long as possible to open. But the new country we've added support for in the app gets a separate project. So we have product, backend, mobile, design, management etc on one, and mobile-country2 on another. This delightfully means a lot of duplication and copy pasting from one to the other, for literally no reason what so ever.
- Everything on Jira is found through a label. Every time something happens, a new one is created. So I need to check for "iOS", "Android", "iOS-country2", "Android-country2", "mobile-<feature>", "mobile-<feature>-issues", "mobile-<feature>-prod-issues", "mobile-<feature>-existing-issues" and "<project>-July31" ... why July31? Because some fucking moron decided to do a round of testing, and tag all the issues with the current date (despite the fact Jira does that anyway), which somehow still gets used from time to time because nobody pays attention to what they are doing. This means creating and modifying filters on a daily basis ... after spending time trying to figure out what its not in the first one.
- One of my favourite morning rituals I like to call "Jira dumpster diving". This involves me removing all the filters and reading all the tickets. Why would I do such a thing? oh remember the 9000 labels I mentioned earlier? right well its very likely that they actually won't use any of them ... or the wrong ones ... or assign to the wrong person, so I have to go find them and fix them. If I don't, i'll get yelled at, because clearly it's my fault.
- Moving on from Jira. As some of you might have seen in your companies, if you use things like TestFlight, HockeyApp, AppCenter, BuddyBuild etc. that when you release a new app version for testing, each version comes with an automated change-log, listing ticket numbers addressed ...... yeah we don't do that. No we use this shitty service, which is effectively an FTP server and a webpage, that only allows you to host the new versions. Sending out those emails is all manual ... distribution groups?? ... whats that?
- Moving back to Jira. Can't even automate the changelog with a script, because I can't even make sense of the tickets, in order to translate that to a script.
- Moving on from Jira. Me and one of the remote testers play this great game I like to call "tag team ticketing". It's so much fun. Right heres how to play, you'll need a QA and a PM.
*QA creates a ticket, and puts nothing of any use inside it, and assigns to the PM.
*PM fires it back asking for clarification.
*QA adds in what he feels is clarification (hes wrong) and assigns it back to the PM.
*PM sends detailed instructions, with examples as to what is needed and assigns it back.
*QA adds 1 of the 3 things required and assigns it back.
*PM assigns it back saying the one thing added is from the wrong day, and reminds him about the other 2 items.
*QA adds some random piece of unrelated info to the ticket instead, forgetting about the 3 things and assigns it back.
and you just continue doing this for the whole dev / release cycle hahaha. Oh you guys have no idea how much fun it is, seriously give it a go, you'll thank me later ... or kill yourselves, each to their own.
- Moving back to Jira. I decided to take an action of creating a new project for my team (the mobile team) and set it up the way we want and just ignore everything going on around us. Use proper automation, and a kanban board. Maybe only give product a slack bot interface that won't allow them to create a ticket without what we need etc. Spent 25 minutes looking for the "create new project" button before finding the link which says I need to open a ticket with support and wait ... 5 ... fucking ... long ... painful ... unnecessary ... business days.
... Heres hoping my head continues to not have a bullet hole in it by then.
Id love to talk more, but those filters ain't gonna fix themselves. So we'll have to leave it here for today. Tune in again for another episode soon.
And remember to always practiseSafeHex13 -
“No we don’t use the time zone info you send on each request. We get all the drivers for the store ID, choose one of them randomly and take their time zone. We have been assuming it will always be the same for all drivers for each store.”
This is my new favorite response to a Jira ticket in this company.
I may have to print it out and hang it on my desk3 -
It is the year 2022.
We have multiple robots on Mars.
We have mRNA vaccines.
JIRA does not yet have a dark mode.14 -
follow on from my last rant.
I've finally gotten my new Jira project. Only thing I seem to have access to change is the Kanban board columns. Still has 50+ fields when creating a ticket etc.
Asked the support team handling the request if this was a mistake. He said no, i'll need to open another ticket to have those changes requested.
Opened and got a reply. Currently there are 2 versions of Jira running. They are working on consolidating them atm and won't help me right now until this is done. I've been asked to re-open my request after the consolidation is done in March 2019.
5 ... fucking ... months, so I can have a competent ticketing process.
He pointed me to a page explaining the move and listing all the changes taking place. Well lets look at the changes they are making that are so critical:
Change 14: Rename "More info" status to "Needs more info".
... Oh pardon me. I didn't realise such critical show stoppers were being addressed. Please do continue. Don't mind me, i'll just be over here taking 4 hours to create an Epic and 6 stories. As you were9 -
Work, the haiku:
(Plus more Dilbert)
“Where are you on this?”
“I’m where JIRA says I am”
“Ok, but how far?”
8 -
Fucking Jira!
You fucking piece of fucking shit. You're about as useful as a nacho cheese enema.
Fuck Atlassian, fuck Jira, fuck fuck fuck fuck!13 -
Deciphering 10-20 jira tickets that relate to 1 feature which aren't linked in anyway beyond titles spread throughout an epic or 2.
Ah the pain of having to go through 200 tickets to find everything you need for a single feature.7 -
Me done fixing a bug.
Me commit the fix.
Me resolve issue in JIRA.
Few minutes later, Me receive a notification. QA reopened issue: "Bug is still there".
Me go have look to Jenkins.
Pissed off, Me respond to QA: "Can you just wait for Maven to finish building the goddamn thing before testing it please?"
Every. Fucking. Time8 -
Do managers not fucking understand that Jira is meant to eliminate all this stupid "What's the status with X?", and "Is Y done yet?" chatter. Our communication channels should be on business logic and other global updates about the company, not about fucking workflow status updates because you have nothing else to do with your day but ping me every 5 minutes.
LOOK AT THE REVIEW COLUMN ON JIRA. I MEAN ITS LITERALLY CALLED REVIEW. SO REVIEW IT AND DO YOUR FUCKING JOB.
I swear the devs consistently have a better overview on timelines and project status than management does - which is sad, because this is literally the definition of management!!!18 -
Me: Wish I got one guilty free murder pass..
God: GRANTED! Which software tester would you like to kill?4 -
Manager logic: Adding "somehow" to the front of the JIRA title for the JIRA description is super clear and helpful.
Example:
Title: Chat screen doesn't work
Description: Somehow chat screen doesn't work7 -
Do you want to really annoy the hell out of someone?
Prerequisites:
1. JIRA account for you
2. JIRA account for the victim
3. JIRA app on victim's phone
Instructions below:
1. Create a ticket and assign / add victim as watcher.
2. Open your favorite IDE or editor with any of your favorite projects with lots of files with minimal sizes.
3. Drag the folder and drop into JIRA ticket window.
4. Enjoy 😎
Don't ask me how I figured this out 😁6 -
JIRA. Fucking JIRA. Everybody just fucking hates it. It tops the list of shit pieces of software by a fair margin, followed by JIRA in second place and JIRA in 3rd. It's fucking unusable without superpowers and endless patience. It does whatever it goddamn pleases and randomly sends your precious input that you so carefully crafted anxiously avoiding to press one wrong key to the happy hunting grounds.
Fuck you, JIRA.
- Every developer. Really every.17 -
QA : There is a bug, come at my desk now !
Me : I'm busy on some feature, can you make an issue on Jira I will fix it later.
QA : NO! It's a major issue
Me : Ok... I come.
* 3 hours later *
QA : I just created you the Jira you asked
Me : I told you, the bug is already fixed since 2 hours
QA : yeah but I will not test it until you mark the issue as done on Jira
.... Are you kidding me ??? So you interrupted me in my work two times for one stupid issue...4 -
Excited for the following upcoming product releases:
Dark Mode GitHub
Dark Mode Jira
Dark Mode Kubernetes
Dark Mode Kafka Streams
Dark Mode WebEx12 -
Employer:"Have you tried JIRA before?"
Me: "I know JIRA, it came from a company called 'Atlassian'. I was interested in their product, but it says that it has 30 days trial. So I didn't have a chance to use it."
After a month..
"Our JIRA is pirated, we will use it in our internal servers"..
Me: (I thought this company got an enterprise product of JIRA).8 -
The sell: “become a designer, change the world”
The reality: “become a designer, create Jira tickets for devs to fix stuff you’ve noticed” -
Pet peeve: When people use "Jira" to mean story / task / sprint / epic.
*Real* pet peeve: When people use it with more than one of the above meanings in the same sentence.
"Will we finish this Jira (story) by the time we close the Jira (sprint) on Monday?"
Dude, wtf. I actually have to decode your sentences to figure out what you're on about. Just learn the right terminology. It's not hard.10 -
Just got asked by our JIRA admin how to add in JIRA add-ons for our self hosted version.
... if you don't know why are you admin then!?3 -
Screw the Chief Technology Clown role...
I'm now officially Chief Babysitting Clown...
Skills I can teach you include the following:
- How to read JIRA tickets
- How to write JIRA tickets
- How to check colleagues' calendars
- How to define requirements in English and not some sort of technologically challenged caveman language
- How NOT to do any programming (since I don't have time for that anymore)
And many, many more! Inquire within!4 -
Tester commenting in a Jira ticket:
"Not testable"
Me thinking:
"Why? 🤨 Has he been attacked by a tiger or something?"12 -
PM: Hey listen, client sent us his feedback about the app that we need to fix, they wont take time.
Me: Sure no problem.
5 Minutes later:
*Receives email*
*checks email*
15 easy tasks that take not time to finish BUT they are put inside ONE FUCKING TASK ON JIRA! WHAT THE ACTUAL FUCK IS THIS SHIT! 15 IN ONE YOU DUMB FUCK!
MOVE YOUR LAZY ASS AND WRITE EACH IN ITS OWN MOTHERFUCKING TASK!
Another reason on why I hate humans -_-1 -
You guys wanna know why I rage so much at the 🤡🤡🤡's I work with?
I shit you not, this is a ticket in our "to do" section of our Jira.
what even is ticket linking??!?!?
what even are tickets??!?!?!
or better yet.... what even the fuck is jira?!?!?! I've only been using it for over a year, give me some time to figure out how to use it!!!!!!
I don't know, maybe i'm the asshole. But at least I don't feel like a 🤡
7 -
We have this incredible Jira system that allows anyone with half a brain to report anomalies, add some screenshots in it, a description, links, everything.
Then WHY THE FUCK would you add a fucking docx file in which there are 2 lines and one screenshot? What blocked you to add the fucking content of your docx shit to the fucking Jira?
I swear to god, some people should be medically forbidden to come close to a computer4 -
I opened a ticket earlier with my automated ticket script, and saw its number, so I couldn't resist.
-
Manager: How's (insert dumbass task that they assigned literally 1 hour ago) going? 😊
Dev: We have JIRA for a reason, you'll see it will be moved to demo / review when it's ready.
Manager: ...
Dev: ...2 -
I'm a software developer. Last week I spent half a day teaching a "Senior Data Scientist" how to use git branches. I spent the other half a day teaching him how to use Jira. Now I'm being told that the dev team isn't raising enough Pull Requests. FML
-
“You have a Jira?”
“You need a Jira, first”
“Open a Jira”
“You need a Jira for that too”
“That Jira is on the wrong board, plus you need to email _this_ form first”
Jira, Jira, Jira-fucking-jira, AAAHHHHHHHHHHH, STOP!
My job appears to be nothing more than an abstraction layer around Jira. A leaky abstraction11 -
That slow realization that you're hitting burnout due to the toxicity of those in non-technical roles above you is wild. Also, Jira, Scrum, Sprints and all the extra bullshit can fuck right off as well.3
-
Fucking kill me. Is this really all we do with our lives?
1,715 JIRA-related emails. ALMOST TWO THOUSAND EMAILS. I mean seriously, that's BY FAR the largest email filter I've got. I mean I had them muted of course, but when you really think about the whole thing... are we just wasting our lives chasing some garbage that doesn't really matter? ugh.
Death approaches...
9 -
Manager: (𝑤𝑟𝑖𝑡𝑒𝑠 𝑡𝑖𝑐𝑘𝑒𝑡)
Title: Something something related to the dynamic display of a button on one of our screens in our UI
Description: Something something completely different related to how entities are filtered on a different screen
Dev: f*&$ing hell, do i have to give yet ANOTHER schooling in JIRA this week?!
I swear they're drunk every time they write tickets.7 -
funniest thing today: PM asking me to create a Jira subtask for EACH class / data type of the data model that I'm CURRENTLY concipating / designing in this story.
maybe I should write a Jira / Enterprise Architect integrated tool that updates Jira tasks based on my modeling actions, and count minutes until our sysadmin arrives at my desk.
jeez, that guy really has a fetish for kafkaesque bureaucracy.🤦♀️4 -
That moment you realise you spent the day skinning Jira to look like atoms material dark theme because a key system is down preventing testing😊
-
JIRA Push Notification: [Task] Assigned to <PM>
JIRA Email: [Task] Assigned to <PM>
Hangouts: <PM> I removed that task from you.
5 minutes later at my desk: PM: "Did you see my hangouts? You don't need to do that task anymore."
1 -
Got a few Jira tickets reassigned to me because the dev who was supposed to work on them got stuck on another project. It's fine, that happens.
I open the tickets. No descriptions for all of them. No screenshots for those reported as bugs, nor any replication steps. No attached test cases or, well, ANY useful information.
I talk to our BA, he says that all information I need are in OTHER tickets on ANOTHER BOARD that business manages but I DON'T HAVE ACCESS TO. Honestly, these shitfucks could've just done simple copy/paste. But nooooo...
So I reassign all the tickets back to their original reporters (business testers) with comments requesting more information.
It's been a week. Now I have no idea what to put in my time sheet.1 -
JIRA, the haiku (w/Bonus Dilbert strip)
Please make a ticket
Please move the ticket you made
Please tag your ticket
3 -
I'm pretty fucking sure that if I were to quit my job, I'd have to gather the fucking requirements, create the fucking user stories, and then JIRA the ever-living fuck out of it before I could submit my fucking resignation.
I just want to write fucking code.3 -
JIRA 2017: "Too many emails? Download the JIRA app and get notifications on your phone instead!"
JIRA 2018: "Too many notifications?" -
I HATE automated messages on Slack
Remove fucking GitHub updates, Jira updates, all this stupid bullshit that pollutes actual communication between humans in all that fucking shit and makes me miss actual messages because I ignored a channel where that garbage cancer shit was set up on?
What's wrong with going to fucking Jira and GitHub and checking how things are going THERE?7 -
Worst Jira ticket I've ever seen:
Title: "It looks f#?$ed"
Description: ""
This gem was opened by the project producer. When asked about it, it was just a mismatch in text margins. -
I find that no matter what I do I have roughly 50 issues assigned to me in Jira, so there's no point in working hard to clear em out. I'll never get to zero.2
-
Headphones on, noise cancellation enabled, Google play music enabled.
Connect to my remote desktop and open Jira
See ridiculous backlog and get to work
(Panda for views)
-
If a tree falls over in the woods..
And important dev work gets done and shipped,
And it's not in JIRA.. did it even really happen..5 -
We use jira at my company. It's great for me, because no ticketing system's UI is worth a shit, but jira's API is excellent. But we're switching to a new system that is an absolute piece of garbage. Every page is 100% Javascript, so no source can ever be viewed, and the URL never changes to reflect what's onscreen. If you know a ticket number, no URL will ever get you straight to it. You have to navigate multiple slow-loading 25MB piles of Javascript to reach what you're seeking. And most damning of all: the new system has an API, but our highest management is withholding access to it, claiming it breeds laziness.
Is amazing the kind of shit you have to swallow when your management has regular meetings with really really super extremely good-looking sales people.10 -
When there is a hard high priority bug come up and someone on the team assigns it to themselves and writes on JIRA: "I volunteer as tribute".
-
JIRA.
Plenty of good things happened at work this year. Then we started using jira. That "heavy" bucketfull of shit though.7 -
Ever had a day that felt like you're shoveling snow from the driveway? In a blizzard? With thunderstorms & falling unicorns? Like you shovel away one m² & turn around and no footprints visible anymore? And snow built up to your neck?
Today my work day was like that.. xcept shit..shit instead of pretty & puffy snow!!
Working on things a & b, trying to not mess either one up, then comes shit x, coworker was updating production.. ofc something went wrong.. again not testing after the update..then me 'to da rescue'.. :/ hardly patch things up, so it works..in a way.. feature c still missing due to needed workarounds.. going back to a and b.. got disrupted by the same coworker who is nver listening, but always asking too much..
And when I think I finally have the b thing figured out a f-ing blocker from one of our biggest clients.. The whole system is unresponsive.. Needles to say, same guy in support for two companies (their end), so they filed the jira blocker with the wrong customer that doesn't have a SLA so no urgent emails..and then the phone calls.. and then the hell broke loose.. checking what is happening.. After frantic calls from our dba to anyone who even knows that our customer exists if they were doing sth on the db.. noup, not a single one was fucking with the prod db.. The hell! Materialised view created 10 mins ago that blocked everything..set to recreate every 10 minutes..with a query that I am guessing couldn't even select all that data in under 15.. dafaaaq?! Then we kill it..and again it is there.. We found out that customers dbas were testing something on live environment, oblivious that they mamaged to block the entire db..
FML, I'm going pokemon hunting.. :/ codename for ingress n beer..3 -
WHY DON'T PEOPLE PUT FUCKING [FRONTEND] AND [BACKEND] LABELS IN THEIR GODDAMN JIRA CARDS
FUCKING FUCK4 -
I had someone reject me the follow me to the parking lot and ask me to teach them Jira in their spare time. 😂😂😂2
-
the amount of micromanagement enforced in our scrum routine is getting ridiculous... but the PM seems to be happy with this
14 -
How can I make my manager understand that performance should not be measured by how many tickets we have resolved?
If the ticket is an easy one then sure 1-2 days is enough, but for some complicated shit or dealing with models that I have never touched before, I am gonna need several days just to understand the requirement.
For some fucked up reason, our story point is in hours, instead of days. So when we say 24 hours, then it's only 3 days.
Another fucked up reason is that my colleagues doesn't seem to mind. I am the most vocal one objecting when got assigned too many tickets. They just joke around and seem to accept it.
FYI, I am just 6 months in and bouncing between 3 projects.
Am I just too lazy or slow?
In my previous company, the devs seemed to be pretty chill, and the project manager only complained when an issue has been dragging on for weeks.5 -
2 months into my first dev job, everything looks like a Jira ticket now.
Mum: wash the dishes
Me: create a ticket for that... i estimate the story points to be 27 -
A custom script that makes a Jira ticket, assigns it to me, marks it as in progress, check out a git branch, set the commit title and the Jira title to my command line argument…. Push, open a PR, and fuck it, merge that shit too.
I checked all the corporate boxes and you got the typo fixed. -
What's the use of implementing JIRA when you'll still demand sending daily reports with time duration for every task?!3
-
There are two jobs I would rather suck dick on the street than do.
Sharepoint developer
JIRA admin
What’s yours?15 -
Hey devs, really need some help here. This is driving me crazy...
We're currently taking issues from the company via mail. We've got a group mail that goes to the three of us at the IT department. Problem is, colleagues just forward customers emails without event trying to help, which means that we get stupid issues like "I can't sign in", and no further information. We're currently using Jira, and I was thinking perhaps we can set up a Jira Service Desk? Then we could have an internal help desk where issues could be submitted, and require some important fields, and perhaps add a checklist. Have you had any experience with Service Desk? Do you think it would be a good idea to have a "normal" person have an account there as well to filter out the normal "Have you tried restarting your computer" stuff? Is it suited for non-developers?
Any other ideas?
Yeay, messy question, but I'm fucking desperate...5 -
Just received a Jira request to remove training videos from the business ethics page or our employee intranet because we longer hold the license's.
HaHa1 -
In these GOT times,
managers will suffer,
PRs will not be merged,
Pivotal Tracker/Jira stories will not be attended to.
Stand-up meetings will be ditched.
Winter is here. -
Since we announced our product yesterday, the bots have started emailing our fuckin support system (which automatically ends up in our Jira Service Desk).
Pound salt you halfwit marketing fucks, you're cluttering our bug reports -
I just want to delete a jira…that’s all just delete it..listen you jira fucks ..just let me delete the fucking thing!!!1
-
Am I the only one the sometimes just makes a PR that won't fix the issue but at least shuts everybody up so I can investigate in peace.3
-
One of our clients asked us to Integrate their projects with Jira, so I got this funny email from atlassian.
1 -
All tech department was really happy when we used Github Projects - managing a project was concise and organised. We loved it.
Then one day, product pushed us all to switch to the fuckin' conglomerate mess called Jira (fuck you Atlassian), which we still hate. So cumbersome, so much unimportant crap features, unintuitive interface, slow .... yes, fuck you Jira, again.7 -
I work in a multinational ..time stamps everywhere without fucking Timezones..fucking Jira shit why is there no TZ on this shit…utter cunts who configured it or the software itself4
-
Project name - "JIRA 2.0"
Description - JIRA seems to not be informing people in our company about much of anything right now. Engineers don't know how to find anything. PMs don't know when things are shipping.
Me: JIRA, you had 1 job!
1 -
So I forgot to put (m) for minutes in Jira, and made them hours automatically, my boss wants to see me
7 -
Just JIRA things:
We've got a very descriptive ticket with the title: "API Interface"
Can't wait for the rest of this Friday to play out, I'm already joyful and in the holiday spirit.2 -
Confluence WYSIWYG editor for tables on wiki pages. Forget about git and GitHub idiosyncrasies, "at the end of the day" project documentation in Confluence and Jira is the real challenge.1
-
If you're filling a ticket on a team, make sure it includes EVERYTHING that is needed to complete the ticket so anyone on your team can complete it, not just the people with institutional knowledge.5
-
I administer Atlassian stack instance (among zillion other things, of course). Once I've got an issue about login problem:
"I can login to Confluence, but not to Jira, could you help me?"
Looking into projects configuration, into user's permission groups in Crowd (both apps are connected, it will be important in a moment)... Everything looks good. Wtf?
Suddenly, I've got this idea:
"What username do you use in Jira?"
"My username."
"What about Confluence login?"
"My email."
Realization in 3... 2... 1...
Wait for it...
Just a little more tension...
"Nevermind, thank you!"
Remember, guys, always give them a chance. Plan for the worst, but hope for the best. And I wish you all only such issues! :-D -
My manager asks for help because they can't suddenly edit their shortcuts in Jira. I can't fix it, and it turns out that it's a bug in Jira which was there since last November.
Nobody has even been assigned to the issue for nearly half a year according to Atlassian's own issues page.
Why would anyone even bother to use Jira at this point?3 -
How to kill Jira Backlog in one simple step:
1) put '-∞' to Storypoints
2) enjoy
(Bottom line: it can be fixed from User Story Map to something normal)
-
I may have watched too much Westworld; I'm naming JIRA tickets with "Analysis - what caused the failure..."2
-
to everyone who complains about poor methodoly usage:
I had a solo ptoject. I was told to do scrum. I had dailies.. with my PM. we were moving JIRA tickets around. -
Reminder, include legal language in next project that says if we're using JIRA then we're using JIRA and not a thousand emails with requirements embedded in spreadsheets and PowerPoints.
-
Half of the day is spent on meetings, and the other half is spent hearing others saying, oohh but do we have a ticket for this task? Should we create a ticket for it??1
-
I hate meetings that could have been just checking the Jira to see what everyone is working on... Getting 5 people together to individually mention what they're working on... So inefficient7
-
I just moved my personal projects over to Jira... since I'm my own PM.. does that mean I hate myself?
-
Go assign a super simple ticket to your "product owner" or "manager" or whoever the hell claims they "work so hard" and "have the vision" or whatever blah blah blah when in reality YOU'RE the one working 12 hour days, completing the features used by THOUSANDS.
Just try it. They'll never complete it. I guarantee it. Here I am looking at one that is three weeks old asking to update the f&*(@#$ credit card credentials for a simple log service to be reactivated.
So sick of this backward world where us devs never get any credit.
Who wants to start a software union with me?2 -
Tutorial: How to get rid of your dev?
1. Find a very old (2+ years) jira task that took a lot of sleepless nights to get resolved.
2. Make sure that your dev is still on the watchers list.
3. Reopen to 'change some labels'.
4. Forget to close the task again.
5. Remove the body. Heart attack will get classified as a natural cause.
6. Close the task.1 -
TIL that Jira comes from Godzilla.
In Japanese, Godzilla is pronounced like Gojira and Jira is just the second half of Gojira.
This also clarifies how to pronounce it.
https://en.m.wikipedia.org/wiki/...3 -
We've been using JIRA for over half a year now, and my colleagues still can't use it properly.
I've never had the problem, but to some amazing technological feat, every time they create a ticket, it "disappears", so they make a NEW ticket with just the title references to the actual one.
Love my daily review of JIRA, it's like a fucking raiders of the lost ark scene.
"ooooo what does this one mean, perhaps there is a clue if i shine a light on it just right"
jesus christ incompetence is rampant
3 -
Logging work in Jira, because it goes against the whole ethos of trusting people to get the work done when they have to log exactly how much time they spent on each individual story. It also doesnt account for pair programming. so 2 people log the same time and it looks like the story took twice as long. I’ll stop now because I’m precariously close to opening the “time based estimates” can of worms and thats for another rant.4
-
We're living in a world where 200 ko of RAM to send people to the moon, but 4 go isn't enough to make Jira fluid, while it's a fucking website.10
-
Working at a different company for a few weeks before getting back to my usual work.
I'm using everything I hate: ReactJS, factories, style through JS, Jira, Teams, TDD...
The only good thing is I'm using TypeScript...1 -
Why are we even using JIRA?
It's clear from the behavior of the rest of my team that nobody ever has it open, looks at it, or thinks about any tasks that would improve the product other than sputtering out the occasional "mArKeTiNg HyPe" with incomplete horrible tickets that are at best barely decipherable.
Honestly, we can save the $50 a month and I'll just use my own personal trello board, the outcome would be the same.
I mean my life is a joke: we had to have a near hour-long google hangouts for literally dragging and dropping the 'demo/review' tickets to 'done' because my colleagues are so incompetent they can't read the tickets and realize which tickets HAVE LITERALLY ALREADY BEEN SHIPPED TO PRODUCTION WEEKS AGO.9 -
It's kinda inpressive to me how everything comes to a standstill, as soon as Jira goes offline, because it's been overwhelmed by stuff going on.
Me and another colleague are waiting for it to get back online, so we can annoy the devs with defect reports again.
Which inturn were due a while ago, but the deployment for testing them wasn't done the whole time, so it was not possible to test anyways. And ontop all of that most of the tests failed, so there are a ton of defects.
Fixing them and bringing the tests on PASS has to happen until tomorrow, because that's the deadline for the release cycle.
Ah and it's roughly 45 tickets.
The next release cycle is like in two Months
You know... the usual stuff 😂😂1 -
Does anyone genuinely have manager(s) who give a shit about your career and growth and not simply the status of your JIRA ? :)
Would love to hear your thoughts :)5 -
When you come back from work after filling up jira, talking with colleagues during too long stand ups and writing documentation it's time to finally sit down and write some pure code.
-
JIRA life:
Project leader proceeds to put what is actually two separate issues in the title. I'm already raging. I go to take a look at it.
I read the description - ANOTHER (this makes it three now) totally seperate issue in there.
Just fuck you I'm so sick it i see it over and over again no matter where I go or what project I work on its all the same bullshit.
"wE wAnT tO cLeARlY dEfINe iSsUeS aNd MoVe RaPiDlY"
YEAH THEN F&Q*@#()#$(@)#$ DO YOUR F$*(@#(*&$ JOB!!!! I'M DOING MINE, IN ADDITION TO DOING YOURS, CLEANING UP YOUR ABSOLUTE MESS THAT YOU LEFT!!!!1 -
Can't wait to get back to work tomorrow, long weekend of family has got me antsy for a jira ticket1
-
returning from 2 weeks of PTO, the haiku
what was I doing?
*Looks through tickets in jira*
gives up. plays halo. -
when you work for Jira and get assigned in Jira’s Jira to write code in Jira Query Language to query Jira’s Jira so other Jira users can query their Jira better
2 -
Fuck you Jira, for your shitty implementation of the board, which causes written comments in tickets to simply disappear.
You clicked on another comment during edit? Say goodbye to what you have just written!
You clicked on the send button to send your comment? Well, many things can happen with our overcomplicated pile of shit that we call Jira. So, your comment might get lost. Fuck you. We are complicated. This shit can happen. Deal with it.2 -
when you spend more time in JIRA explaining the client that their bug is not a bug but misconfiguration on their side than actual programming. :-/
error between chair and keyboard.1 -
So after multiple hours of wrestling with Jira I finally managed to autofill fields in the service desk. How? By installing a plugin to show message boxes and injecting JavaScript through it, what else?
Fucking wonderful piece of crap :)
Next up: automatically capture errors triggered by employees with Sentry and raise Jira requests. "A button didn't work" isn't enough god damn it. -
Product manager keeps fucking with my Jira board, changing names of tickets that he's not even the reporter of and none of his names make any sense. I keep thinking my tickets have disappeared. He doesn't understand how Jira works and confuses the shit out of me.4
-
when you work on a bug about fixing mistakes made on a story completed by somebody else
you then get approached with having to do petty unrelated UX stuff in the neighbouring area and the administrative nonsense with it
fuck u jira2 -
Spent an entire day clearing the backlog of the previous sprints in JIRA. Now i am seeing jira numbers everywhere :/2
-
for my job I need to know,
Programming, C#, Optimization, Multithreading and Async code, Working certain tools, Reading difficult written code, Understanding, Physics, Networking, Rendering, Codeloops, Memory management, Profiling tools, Being able to make Jira tickets and read Jira tickets. Understanding source control branching, merging, push and pull. bug fixing.
And I write almost 1 line of code a week on average..
I'm a programmer.3 -
Is it just me or Jira has been getting so much worse over time, that I now don't even want to touch it?9
-
JIRA queue just dropped into the single digits for the first time in weeks. It's getting me right in the feels.
-
I wonder...
On a global scale, how much of Google's storage space is being consumed by unread JIRA emails.3 -
Our team uses story format titles for JIRAS like As a ..., I want...
But in our git repo, a lot of people create branches using the same name:
{JIRA-ID}-as-a-...
And I'm always like why the fuck can't you take 5s to name your branches more descriptively? I usually name mines using some keywords from the Jira Title
But wondering now what do you all think/do?2 -
Jira workflow requires dept manager to approve and assign new issues to developers. He does this once a week. 😑5
-
So I was in a training course today teaching us the basics of JIRA. (Turns out when they said basics, they really mean basic. I learnt nothing) Out of the blue, mid way through the lecture, a lady in her late 40's asks, "Can you copy and paste into JIRA". The worst part is, is the probability earns more than double my wage...
1 -
You know how people are making fun of duo lingo birb getting’ all in your business about learning new language & not missing out on your daily exercises?
Well, our jira just upped the ante.. Boss asks why task xy is assigned to him.. um dunno?! I go check activity, as I don't even remember doing anything with that task recently..
All the dates, 'just now' remarks etc. on activity tab are in Russian.. WTF jira?!
ты пытаешься мне что-то сказать? -
Happy Monday Ya'll, may your code be bug-less and JIRA unfilled.
(I know none of this will happen but damn it dream will you) -
Open a older case in #JIRA and either I'm in past or this thing is messing with me today Jan 30, 2018
2 -
Does anyone else's manager measure their performance based on jira ticket count or merges to master? It feels like a new lines-of-code measure to me...5
-
We often give access to a product owner from the customer on our Jira to keep up a good communication and everyone stays up to date as everything is on the board and not hidden in emails or paper notes on the desk of the guy that is on vacation.
So far, so good
Our customers really like this as they can comment on tickets and they are integrated in the workflow because they can push into the backlog and can review finished tasks.
It is just getting better for everyone so where is the rant?
One project is just a dump of shitty mixed content tickets. But how? They look really neat. There are tickets like "fixes from meeting 20th of may" which are initially well structured with approximately 4 subtle changes to the UI and some explanation and screenshots.
PM says: Good ticket. There you go ticket, into the customer review loop of doom.
20 comments and 13 status changes later. Point 43 from comment 17 is referenced in comment 20 to keep on hold as a third party needs to give feedback, point 7 is still not solved correctly as dev 2 was not aware that it was already discussed and changed in the ticket "Call from 25th of may" where in addition the resolution of points 5-12 were requested with an additional excel file to import.
By now we have the 8th of august and literally 17 of these kind of tickets.
I guess we need to improve the workflow and request a new product owner. But this far I just table flip everytime I get one of these tickets assigned.2 -
My manager always tell that we're less process oriented and self sufficient.
Later on, I understand what that means
- Poorly written JIRA tickets
- JIRA tickets with only title, rest for you to fill
- Two teams did same task, client side team pushing their change directly on master, while mine still waiting on code review will eventually get rejected
- Client writing raw SQL in ORM framework instead of using any single feature of ORM.4 -
Dev management high muckety muck: "Even though I never speak to or communicate with any of you personally, my Jira charts indicate that you are sub optimal." Absentee managers can't help but be dickheads.
-
if you are a good developer, been dispensable in a project is like quicksand: the more you try not to be, more important you become ... and you die choked by Jira tickets and anger1
-
Jira for one of my personal projects has an epic called "progress repo". No description. No child tasks. It seems vaguely famiar, but I've got no idea what I was talking about 4 weeks ago...1
-
Out company standard tools, which we are all supposed to use... (JIRA, confluence) .... IT had blacklisted docs.atlassian.....2
-
Back to Excel for control project, sih 😢, just because my non tech boss can't work with JIRA and it confused him. Do you guys know any idiot friendly control project before I having a heart attack?2
-
Each day, I read the vast swath of ticket hell hole that is our JIRA.
I read tickets that are written by people with not just 0, but an undefined understanding of technology...
I read tickets that are technically impossible due to this 0 understanding...
And finally, I laugh in bitterness seeing the time estimates stack up to months and months worth of work for which the managers expect to be done in 2-3 weeks 😂3 -
Clicked "Reader View" on a Jira card in Firefox. Firefox displays a JSON object which it estimates is going to take me 17-20 minutes to read.
Go home, Firefox, you're drunk. -
Honest question: Is Jira really that bad?
Iam using Jira. It is not blazing fast nor is the UI amazing but I wouldn't rate it so badly.
That said, when the UI gets cluttered it's mostly company-internal stuff that fills up space (not only Jiras fault). I also don't use confluence.
But I see so many rants on it, is this just people jumping on the hate-hype-train?11 -
So we're using Jira Wiki for all the documentation related work. It's hell rich with features as they describe. But for me easiest way is to write doc on markdown and then copy paste on Wiki. Highlights code, format tables and aligns paras perfectly.2
-
For you Jira users, as song:
(to the tune of "Everything is Awesome" from The Lego Movie)
"Everything's P-Zerrrooooooo!!!
Everything is due day before yesterdaaayyyy!!" -
Uh oh, watch out for the latest security issue in Atlassian products ...
https://confluence.atlassian.com/ji...3 -
> Get blamed because I don't update my jira ticket
> Can only sign in Jira randomly 20% of the times -
I'm curious - how strict are you (or how strict is your lead / manager) about keeping stuff both detailed and up to date in Jira (both in terms of sprints & tickets)?
I've always drawn a pretty hard line with this - stuff in our Jira environment always has a detailed description, approximate estimate, is kept up-to-date with who's working on it, assigned appropriately, etc. But others I've spoken to seem to barely care if any tasks are in there properly at all.2 -
Atlassian needs improvement!
Screenshot from the Jira "Accessibility" settings page where I hoped to find a dark mode switch.
When I wanted to send them feedback about the settings page, the feedback form failed, cluttering vintage style error messages with poor UX writing all over the page.
> Help us improve!
>
> We’d love to hear more about your experience with the new accessibility settings in Jira. Any thoughts on what you liked and where we could improve are more than welcome.
> Oops! Something went wrong...
>
> There was a problem submitting your feedback, likely due to the configuration of this form. You might want to contact the site owner to let them know about this issue.
P.S. Thinking of accessibility: there is not way to enter an ALT text to image uploads on devrant? seriously?
6 -
Project Lead: The DevOps department just got a GitLab instance installed on our internal network. We're gradually going to move all our projects onto it and move away from BitBucket and Jenkins really soon.
Me: Awesome!
Project Lead: We're still using JIRA and Confluence for issue tracking and documentation though because the higher ups said so.
Me:
2 -
I had a gentleman tell me I was overqualified, and then proceed to ask me for help with Agile software (jira)! 😂 I gave him my card!
-
Today we received a new scrum master. Seems nice enough.
Now he wants to remove the fucking swimlanes from OUR jira board and change them into separate sub tasks.
Wtf.4 -
When the product designer ask me to move my bug fix Jira ticket back because there's a style change.
-
I'm looking for a good JIRA app for Android. I've been using JIRA in Motion, but it lacks flexibility.1
-
Dear JIRA... Fuck!
Why can't you offer integration with TFS? You used to! Now you'll go down in the bag of unused software. Right next to iTunes for Windows.1 -
fuck Jira's 5 days ago date format.
I hate that i fucking have to inspect it every time to get a normal date.7 -
The moment when the UI designers had included their design as a zeplin link in your Jira story. You finished coding it, the designers made changes to it and expected me to magically know about it.2
-
Received an email -
"Hi,
Wanted to connect with you as Mr. X suggested you can provide an architectural on the JIRA system."
How vague can things be? Lost as to what should be the appropriate response.4 -
Sometimes I really have a feeling that God invented Jira to punish me
I really hate it . It's like working with an OCD and sinile old man .
More over this Jira comes with Entourage of duchbags that suppose to support it, but are stupid as fuck.13 -
I have come to an interesting realization. I am nothing more than an abstraction layer around Jira.1
-
Customer calls
Talking about some new feature he haven't totally thought about. so i tell him to think about it.
Talking about a bug, but can't reproduce it.
Talking about another enormous new feature but halt it after hearing the initial estimation.
Total time waster = 1.5 hours for every day.
DON'T LET CUSTOMERS WASTE YOUR DEVELOPMENT TIME.
instead of talking - use project tracking software (i.e. JIRA) -
they're having me log my time in 30 minute increments, with each 30 minute block assigned to a jira ticket, as well as keeping track of my slack status throughout the day3
-
I spend the first 30 min of my day, every day, cleaning up the shit storm that my "PM" hacked together in JIRA. I really wish she would be taken off this project.1
-
So I accidentally used an email as a username to create an account through Jira for mongodb to report a bug.. That apparently breaks the entire Jira login system. I cant recover my account, and I can't create another account because my email is already in use.. Thanks Jira for deciding I'm going to bar before I go home today...9
-
Is there any alternatives to Atlassian's Confluence and Jira?
We used to use GitHub projects and wiki, but "the business" wanted a more formalised process and access controls on kanban boards and backlogs.
We started using Jira and Confluence last month, but Jira have been incredibly slow with a horrible interface also Everytime I create a new issue it feels like I'm wasting a lot of time compared to the time needed to setup an issue on GH and add it to a project board, plus the entire team is used to using markdown which doesn't work great on Jira.
I've looked for some alternative but I wonder what you are using out there!5 -
The company i work at switched to Jira today. Is there anything I should know? What do you guys think of Jira12
-
Questions more then a rant...
I've moved from being a lead on imploring DevOps and Agile practices in a large Telco to now working for a security consultancy... The team I'm with are s*** hot when it comes to SecOps (which is why I changed jobs) and I've been hired to he the automation and working practice expert on the team. Already got some of them learning Ansible which is a great start!
I've got delivery now being pushed to Git and all client work being tracked in Jira and properly documented and collaborated through HipChat and other CI tools on the way....
My question is this... Does anyone have some awesome resources to teach people Git, Jira, Jenkins, etc. quickly without forking or branching out on expensive training? Focus on being a technical but consultative team. Ideally just wanna pull some awesome guides and make. My own commits on them for the team... Please fire a story or epic away!1 -
When I was in my previous company, we used a Jira tag named as 'IE Issue' 😆
The best part is, even clients understood it!
Ouch!!! 😆 -
My boss yelled at me Monday for brining up that no one in the office is a fan of Jira.
He yelled and gave 4 rules.
1. Task Numbers
2. Multiple Project Overview
3. Integrates with Github
4. No one bitches
I spent the day uploading data from Jira into clubhouse2 -
Digital transformation is pain in the ass, my customer migrated project management from self hosted jira to atlassian cloud.
Results:
I am finally able to login to this new amazing jira that looks completely different but still nothing is optimized to laptop screen so looks crap as before.
My issues are now assigned to not existing user.
At least I remember how to use basic JQL and reassign issues to me.
I feel bad to other team members.
Great waste of time.7 -
Aren't we, software engineers, the whiniest sort out there? Jira ain't good, Redmine ain't good, nothing can satisfy our needs for lack of commitment towards project administration. 😂
I just catch myself sometimes writing obscene amount of hours in timesheet under "US management in Jira" topic or similar. 😂2 -
I worked as an backend dev the last 2 years and was maintaining and connecting external APIs to our system. If one of these did not work properly or their test system went down I needed half a fucking day closing all JIRA issues named "EXTERNAL system not reachable" . Who needs speaking error messages anyways...
-
Can anyone explain why the Assign Issue and Resolve Issue dialogs in JIRA are modal, so that I can't look at the issue I am assigning/resolving while writing my comment and filling out all the other mandatory fields?
And if you close and reopen the dialog, all your changes are lost. Second tab it is...1 -
is it sane to choose Notion instead of Confluence and Shortcut (Formerly Clubhouse) instead of Jira, or do I come as a total hipster?
Or better yet, instead of Shortcut or Jira, choose Todoist?5 -
Jira really fuckin gets on my nerves a lot. It has so many features, but fuck do those features behave strangely. It's like if you reorder that card on me one more god damned time, I will feed your fuckin testicles to you.1
-
Tempo has lost its reference to the issues on which I'm trying to log work. Used to press 'W' on an issue and that issue was automatically selected as "Issue key", but now I have to select it manually. A small problem I know, yet it annoys the crap out of me.
-
Team Lead (not my team, thankfully) sends outs a team-wide message (in their exact words):
"please DM me with the task link if you are adding any new tasks in Jira. This is to make sure that i am aware of any ad-hoc task coming up in the jira queue and also to make sure that all the task are following a common template."
Interpretation : "I'm just too lazy to look at each jira issue after the last one that I followed up on (which is my job BTW). So I'll add some extra work for you to explain everything to me on DM"
Way to go for killing productivity. ¯\_(ツ)_/¯
Thankfully, this is not my team. If they were my team lead, I'd be super furious. I'd even report it to upper management. I'd even offer to do their job and let them do mine. I think their job just got so easy if everyone was to go report to him like that.3 -
Is there anyone out there who uses absolutely everything JIRA has to offer? I've worked with it since starting my career and I still find it a massive fucking overkill.
-
If you have a Google document related to this JIRA issue, can you just take the 30 seconds to flippin attach the link to the issue please? Don't make me search Google Drive to find your work.
-
Fuck Jira. That motherfucker sucks up almost 500mb of my ram and I need that shit since I'm running vscode and 5 other tabs minimum. And I only have 8gb how low it is right (!). Even my PC is idle whenever I open jira it starts to hangs so badly WTF YOU CODDED THERE ASHOLES CHECK YOUR CODE. I needed to get this off me I'm still mad that there is no console jira with only text
-
Have you guys had any trouble trying to get the BAs to use JIRA for issue reporting/management? The dev team just upgraded to new JIRA and we are getting hard pushback... they're wanting to stick with 1-4 excel spreadsheets on a share drive...3
-
Has anyone used CA's Rally for issue tracking? Is it as bad for devs as I've been warned?
We are being forced to use it instead of Jira because of the pretty reports it generates for management and I am kind of scared...5 -
Ahh most of my development time includes, handling JIRA tickets and arranging them in their respective state.. 😅
-
JIRA BULK DELETE USER!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!3
-
This is a repost of an original rant posted on a request for "Community Feedback" from Atlassian. You know, Atlassian? Those beloved people behind such products as :
• Thing I Love™
• Other Thing You Used One Time™
• Platform Often Mentioned in Suicide Notes, Probably™*
Now this rant was written in early 2022 while I was working in an Azure Cloud Engineer role that transformed into me being the company's main Sysadmin/Project Manager/Hiring Manager/Network Admin/Graphic Designer.
While trying to simultaneously put out over 9000 fires with one hand, and jangling keys in the face of the Owner/Arsonist with the other, I was also desperately implementing Jira Service Desk. Normally this wouldn't have been as much of a priority as it was, but the software our support team was using had gone past 15 years old, then past extended support, then the lone developer died, then it didn't work on Windows 10, then only functioned thanks to a dev cohort long past creating a keygen....which was now broken. So we needed a solution *now*.
The previous solution was shit of a different tier. The sight of it would make a walking talking anthropomorphised sentient puddle of dogshit (who both eats and produces further dookie derivatives) blush with embarrassment. The CD-ROM/Cereal Box this software came in probably listed features like "Stores Your Customer's First AND (or) Last Name!" or "Windows ME Downgrade Disk Included!" and "NEW: Less(-ish) Genocide(s)"!
Despite this, our brain/fearless leader decided this would be a great time to have me test, implement, deploy, and train everyone up on a new solution that would suck your toes, sound your shaft, and that he hadn't reminded me that I was a lazy sack enough lately.
One day, during preliminary user testing I received an email letting me know that the support team was having issues with a Customer's profile on our new support desk. Thanks to our Owner/Firestarter/Real World Micheal Scott being deep in his latest project (fixing our "All 5 devs quit in the last 12 months and I can't seem to hire any new ones" issue (by buying a ping pong table)), I had a bit of fortuitous time on my hands to investigate this issue. I had spent many hours of overtime working on this project, writing custom integrations and automations, so what I found out was crushing.
Below is the (digitally) physical manifestation of my rage after realising I would have to create / find / deal with a whole new method for support to manage customer contacts.
I'm linking to the original forum thread because you kind of need to have the pictures embedded in said reply to get really inhale the "Jira-Rant" ambiance. The part where I use several consecutive words as anchor links to tickets with other people screaming into the void gets a bit sweet n' savoury too - having those hyperlinks does improve the je ne say what of it all.
bit.ly/JIRANT (Case Sensitive)
--------------------------
There is some good news at the end of this brown n' squirty rainbow though!
Nice try silly little Jira button, you can't ruin *my* 2022!
• I was able to forget all about Jira a month later when I received a surprise vacation home! (To be there while my Mom passed away).
• Eventually work stress did catch up to me - but my boss thoughtfully gave me a nice long vacation! (By assaulting *while* firing me (for emailing in a vacation request while he was a having a bad (see:normal) day))
5 -
Our Jira does reindexing every night. At that time no issues could be created or resolved.
It just tells us to go to sleep in its own weird way. -
Submenu Boards doesn't show in Firefox 45.5.0 when viewing a single issue. This is really frustrating as I can't move quickly between the sprint board and a specific issue. What also sucks about jira is that there is no way to report bugs like this (perhaps Atlassian sincerely believe that they never have any bugs in their products), leaving devrant as the only resort to let out steam ;)
-
never realized how much of a pain it is to try and write good jira tickets that other people who are unfamiliar with the project can pick them up2
-
Jira on Android 🙄
I had an overview of the backlog, blocked, active issues, could see who works on what and so on ...
Accidentally pressed the back button, returned to the project. Now it's a single big list with only issue type, description and deadline. It's pretty much a guessing game, which feature is open. Their seems to be no way to change that, not even deleting any data.
How did this happen?? Let me change it back!6 -
Who wants a simple bash script for those screen recordings you wanna convert into a gif to upload to your JIRA or github or whatever?
https://gist.github.com/christhomas... -
Why can't Jira support standard markdown (as defined by Daring Fireball / John Gruber et al)?
Why does it need an own markup syntax and even fail with it. Using ticks ` for code once worked, now it lets the first tick stay, eats the first code character and highlights it as code. Just why?!6 -
What's your team's best practice when using JIRA (on premises or cloud) and VSTS or GitHub?
Who manages issues/tickets and are they duplicated in both locations? Is one for PM only and other for Devs??
We have both tools and I'm trying to figure out a workflow that doesn't kill devs and PMs.
We have Office 365 so I heavily use MS Flow to help (Jira bug turns into vsts work item) etc, but any insight from anyone who has a similar setup would be appreciated! -
Jira is powerful tool, especially when we combine it with Bitbucket. But, have you ever worked in a company where for example creating feature branch or merging PR changed jira ticket status? Personally I have never seen such automation, even if all clients I have worked for always complained about dev not changing statuses in jira.5
-
Best tool to manage multiple software projects? I have like 5 of them at the moment and I'm the only one working. Already tried JIRA, Trello but one seems like an overkill and trello is too simple.4
-
Why on earth does the Bit Bucket user search when assigning an issue bring up every bloddy user until you typed their name fully.
Surely, team mates should show first.
Maybe JiRA is better?2 -
Does anybody know how to make the story points from sub-tasks in Jira count towards reports when they're completed?
This graph is completely meaningless.
1 -
!rant
So, why is everybody's answer for a windows based git server bit bucket, but Linux does it naturally? -
I'd like to learn SCRUM/AGILE/JIRA or whatever management thingie is available out there that helps to manage projects in a team. anybody can share any link/blog/video? thanks6
-
Why is everybody writing Jira comments as emails?!! If they write 5 comments two the same issue they use the same format.
Hello X,
....
Thanks,
Y
Now I have to respond the same way.... -
One of the best product feature updates (though it's not "very" recent) that I really found interesting and useful from Developer perspective is integration of JIRA cloud with GITHub and how it uses issue key to associate the commit.
I makes things a bit easy while working in DevOps model :)
Please feel free to post your reviews.
Martin Owens, a.k.a. doctormo
Man's got what it takes to be a core contributor of Inkscape and a lot more. Th... [read more]