:small_red_triangle: JIRA priorities




  • Impossible Mission Players - A

    Uhuh. Migration gone bad?


  • :belt_onion:

    Maybe they were supposed to all look like nuclear mushrooms because each bug is one too many...



  • I wish to assign this post a priority. Some form of reddish upward arrow seems appropriate...


  • Impossible Mission Players - A

    @JBert said:

    Maybe they were supposed to all look like nuclear mushrooms because each bug is one too manyactually always top priority..

    FTFR


  • Winner of the 2016 Presidential Election

    Seems like a manager chose the icons



  • Why is Low below Trivial and Minor?


  • Discourse touched me in a no-no place

    @Nocha said:

    I wish to assign this post a priority.

    <span style="color: red"> :fa_arrow_up: </span>



  • What does trivial mean? This always bugged me. It would make more sense to have 2 or 3 :

    1. Fix your shit now
    2. Fix your shit when you can
    3. I don't care about your shit, but here's a bug

  • sockdevs

    @Eldelshell said:

    What does trivial mean?

    IME, a zero-impact bug/cosmetic issue (like a spelling mistake) that's fixable in seconds



  • OK, but how is that that you explained a priority compared with "Critical". Yes, it's " trivial" to do but it can have high priority. This is why it annoy me.


  • sockdevs

    Trivial priority == We don't really care tbh


  • Discourse touched me in a no-no place

    It helps to split Urgency from Priority.


  • Winner of the 2016 Presidential Election

    I'd say that Urgency == Priority. Shirley you meant to say that Priority and Estimated Cost should be separate?


  • area_deu

    They use :heart: for that on meta.d


  • Discourse touched me in a no-no place

    @jira_guy said:

    No repro...

    @CreatedToDislikeThis said:

    Why is Low below Trivial and Minor?

    No idea. They seem to be in no particular order on our instance either.



  • I think that list is very useful for handling the most urgent stuff with highest priority:

    • ignore everything marked "Critical" (for that's mostly "That button is the worst wrong shade of pink it could be!"

    • work on everything else, items marked "Low" first, because that's the ususal irony and the best way to make something stand out

    • Next, ignore "Trivial" because that's what the users think is trivial to fix

    • Next, go for Major, then Minor, then Medium, then High.


  • Discourse touched me in a no-no place

    @asdf said:

    I'd say that Urgency == Priority.

    Nope. Thank you for playing.

    Urgency is one of the factors, but is definitely not the only one. Importance and Urgency are largely orthogonal (some things are both, others are neither) and it is the combination of the two that gives priority. If you only ever do what other people tell you is urgent, you miss out on many things that are key to allowing you to efficiently deliver what they ask for.

    Which sounds trivial. It's not in reality. It's very hard to remember to deal with the things that are important but not urgent, especially when someone's shouting at you over something that is urgent but not important…


  • Winner of the 2016 Presidential Election

    @dkf said:

    Importance and Urgency are largely orthogonal (some things are both, others are neither) and it is the combination of the two that gives priority.

    Okay, that may be true. But would you trust anyone to fill out those two fields in the bug report form correctly?



  • I love how Blocker, Critical and Top 10 are mutually exclusive. Also, if I'm not mistaken, I can assign Top 10 priority to any number of issues, not necessarily 10?


  • Discourse touched me in a no-no place

    @asdf said:

    But would you trust anyone to fill out those two fields in the bug report form correctly?

    Oh dear me, no! I wouldn't let anyone outside the dev team even see them…



  • @dkf said:

    I wouldn't let anyone outside the dev team even see them…

    Our policy only "critical" issues get published. Which is why a lot of tickets get downgraded after they are marked as Done :smile:

    We have a matrix we are supposed to use to determine priority, but about 90% of tickets are marked as "major" - probably because that is the default. There is a push to mark them properly (most would actually fall into "trivial" because of the limited scope they would have).



  • @dkf said:

    It helps to split Urgency from Priority.

    We use Priority and Severity, which generally seems to make sense to people (along with tooltips on both fields describing the various levels with concrete examples).



  • We have Priority, Severity, and separate Top Priority flag, and separate Blocker flag. And all issues are resolved in first-come-first-served order anyway. So...



  • My favourite feature of JIRA is how you can't order by sprint.

    When I want to see the oldest/current sprint items at the top of my list along with critical bugs, I can't. I have to rely on priority/due date/etc.


  • mod

    @Shoreline said:

    you can't order by sprint

    Lolwhat? I just tested this, I certainly can.

    Sorting is only done on columns you can see, s you have to go to the "Columns" dropdown and add Sprint to the view you're looking at. Then you can sort by it. I can also filter by sprint, so I can limit my search to critical items in the current sprint.



  • @dkf said:

    It helps to split Urgency from Priority.
    Realistically there is only two levels.
    1 Gah! Fix this now!
    2 I forgot about this one.


  • Discourse touched me in a no-no place

    Any of you guys want to do my JIRA install and configure? I "accidentally" corrupted our current install during a migration (what the fuck kind of enterprise software doesn't support multiple servers?) And "failed to notice" that the wanker who configured it originally directed backups to the same server which I "accidentally" told IT to nuke after the migration.



  • Dwarf Fortress uses a very simple scheme:

    There are these options for severity:

    • feature
    • trivial
    • text
    • tweak
    • minor
    • major
    • crash
    • block

    They are ignored.

    There are these options for priority:

    • none
    • low
    • normal
    • high
    • urgent
    • immediate

    They are also ignored.


  • Winner of the 2016 Presidential Election

    @DogsB said:

    Realistically there is only two levels.

    There is also 3: "Shit, we should really do this, but I don't have time right now." The kind of obvious bug and/or misfeature that constantly annoys you, but that nobody has time to fix.

    Then the bug stays open for at least 2 years until it gets accidentally fixed or the feature suddenly only takes 50 LOC to implement because of other changes.



  • @Shoreline said:

    My favourite feature of JIRA is how you can't order by sprint.

    A lot of "order by" stuff in JIRA isn't controlled by the "obvious" order (for example, version 1.3 comes before version 1.6), but by how those things are listed in the Admin console.

    Version numbers, for example, are that way. JIRA doesn't even attempt to apply sort rules to them, it just sorts by whatever order your admin set them up in. (They can easily re-order them once they figure this out.)

    It wouldn't surprise me if sprint ordering worked the same way.


  • mod

    @blakeyrat said:

    A lot of "order by" stuff in JIRA isn't controlled by the "obvious" order (for example, version 1.3 comes before version 1.6), but by how those things are listed in the Admin console.

    Which makes sense; version "1.7" might come after "Version 1.6" because someone decided they don't like typing the word version over and over, and version "Waffle" might come before version "Pancake" because the person in charge of names is a fucking idiot.



  • Our sprints are named after birds. So we're always like, "does Ibex come before or after Ostrich?"


  • mod

    They're not in alphabetical order?! Idiots.

    Ours are comic book characters: Ant-Man, Batman, Captain America, DareDevil Doomsday (the project kind of started going off the rails during Captain America, so we got a bit more pessimistic in our naming).



  • @blakeyrat said:

    Our sprints are named after birds. So we're always like, "does Ibex come before or after Ostrich?"
    What fucking moron came up with that idea? You in a place of work or a day care centre?

    *edit I use to think feature number naming convention was stupid instead of acronyms.

    :boy:What's the name of the branch now?
    :older_man:I think it's FL989 now?
    :black_joker: They changed it FL999 yesterday.
    :boy: I'm changing it to SAPD "slow and painful death"

    *another edit: In the same place the meeting rooms were named after rivers. They replaced the doors one weekend and didn't put the name plates back correctly. It was fucking anarchy.

    Although another place I worked has sensible names for meeting rooms. Blue Five. Blue room fifth floor. The room names matched the colour the rooms were painted.



  • Dare Devil is a really fucking lame hero, so you could have kept the original name. Then followed it up with, say, Bouncing Boy if stuff is still a disaster. Or Matter-Eating Lad.


  • mod

    I honestly think we liked naming the doomed release of a doomed project Doomsday :)

    I think the next one is Elektra?


  • sockdevs

    They picked Daredevil over Deadpool?



  • I'll give you $5 if you manage to convince people to use Fletcher Hanks heroes, Stardust the Super Wizard, Fantomah (good claim to the first female super hero in history) and Big Red McLane, King of the Northwoods.



  • @Yamikuronue said:

    Lolwhat? I just tested this, I certainly can.

    Great. I must have been using an old version. I wouldn't have put it past the company I was with to cheap out on the issue management system.

    Maybe the company I was in had this version or something.

    @blakeyrat said:

    ... whatever order your admin set them up in.

    I don't think I got as far as experiencing this functionality, but I can see a use for it.

    Of course, alphabetical ordering by default would be cool.

    @blakeyrat said:

    Dare Devil is a really fucking lame hero

    @Yamikuronue said:

    Doomsday

    I guess the point is salvaging some coolness from an awful situation.

    @Yamikuronue said:

    Elektra

    That bad, huh?


  • sockdevs

    We'll know how bad it really is if H is Howard the Duck


  • mod

    We'll know how bad it really is if we get to H. >.>

    (For those of you with Lounge access, this is SparkleKitten, so....)



  • We're currently in Sprint 76.



  • I had a look and across the teams around here it's either purely sequential like TEAM-XXX or something like TEAM-Y16-W03 where W03 references the sprint start week (in theory).
    Huh ... rather sane options.





  • @dkf said:

    Importance and Urgency are largely orthogonal

    What do you mean, "largely orthogonal"? Do they have eight sides or not?!



  • @ben_lubar said:

    Dwarf Fortress...

    ignored.

    That's right.



  • @blakeyrat said:

    Our sprints are named after birds.

    Ours are named after numbers. (To be precise, they're named after the project milestone at the end of each sprint, but, nevertheless, numbers.)


  • Discourse touched me in a no-no place

    @tar said:

    Do they have eight sides or not?!

    Of course they do! How else do you think they'll tesselate?


  • sockdevs

    @tar said:

    orthogonal


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.