|
Hi All,
Jira a wonderful system for bug & issue tracking... However if you take a couple of days off you get buried with tickets. Most of the tickets I have come across are asking me why I haven't resolved an issue raised by another ticket, which was raised by another ticket and on... Much digital digging turns out that it was an issue that I had fixed just after it came to light marked it on the fix sheet. However as it was marked as fixed to make someone happy a fault had to be raised in Jira, which generated a 'number' which had to have the 'code' applied to it generated by the 'Zephyr' thing.
Good Grief! I spent over an hour to find I had done what was the cause of this thing to work 'Smarter, not harder' 
I had better end there tickets are piling up!!
|
|
|
|
|
Perhaps it should be renamed. How about 'Avalanche'?
Edit: Or 'Snowball'?
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I don't care what its called, it gets in the elephanting way! You spend more time trying to tell the system you are doing your job than do doing it!!
|
|
|
|
|
glennPattonWork wrote: work 'Smarter, not harder'
Be smarter, not work harder.
I would suggest delegate, delete or disable.
|
|
|
|
|
Oooh how I wish I could... new company new rules... 
|
|
|
|
|
Hmmm... you talk as if you were blaming Jira, and not the way your company uses it.
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
True, I think it for use in software development is good, however trying shoe horn Hardware into is asking for trouble...
|
|
|
|
|
Why? Don't both hardware and software implement algorithms? Why should then so different approaches be needed that shoehorning is required?
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Now, suppose your company is using Jira for managing the software development lifecycle...
|
|
|
|
|
That's the point, it appears to focused to software, I tend to play with hardware...
|
|
|
|
|
Didn't you know that Jira stands for "Junior IRA" 
|
|
|
|
|
Could explain alot... 
|
|
|
|
|
When the system controls you rather than you control the system, that is when you know you have a bad implementation and/or gone too far with business processes...
It applies to anything...........
|
|
|
|
|
Count yourself lucky - where I work we have 4 separate ticketing systems some of which vaguely interact with the others and the same ticket is usually reproduced on at least two of the systems, each of these systems holding some of the 'truth' for a ticket.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
|
Oi! I clicked on that!
Here's some Jan Terri[^] in response
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Highly educational, never knew such beauty existed
|
|
|
|
|
Our beef with JIRA is all the spam emails it generates.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Tell me about it! 
|
|
|
|
|
Same here. They really need to make finer grained settings for email than all/nothing. Clarification edits on a ticket assigned to me, or "how do I test this" comments from QA are useful email that I want. Organizational edits (eg setting an epic, tagging a bug as in the web site vs a mobile app, etc) are rather meh. State transitions are context sensitive - I don't need an email about transitions caused by something I did (eg creating a branch for the bug, creating a PR, merging the PR, etc); but one's for activity from other people can be useful (eg QA bumped a change from test to todo because they found a problem) - and complex enough that the level of control I'd like really would probably be a phase 2/10 feature. Others are utterly obnoxious, I don't need 20 email's for each of the 20 open items I've got being moved from Sprint N to Sprint N+1 because N was closed, at most a single email about the new sprint listing all of the affected items would be useful, and at that since it affecting everything in the sprint is a given I don't even really need the list.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Amen, preach it, brother! I no longer need a calendar to know when I'm in a new sprint.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Set up a separate Outlook folder, make a rule, never see another email! which in itself will solve one set of problems and cause another set...
|
|
|
|
|
Eve's gig goes green? (7)
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Veggies!
eve's gig [goes] veggies [ANAG]
green veggies
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
Didn't think it would last too long, but I liked it!
You are up tomorrow. 
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
