Using Discourse as a mere bug tracker is for pussies!
-
Kanban Board
:discourse2: Summary Kanban Board allows you to display and organise topics using a kanban board interface. 👓 Preview Preview on theme-creator.discourse.org 🛠 Repository Link https://github.com/discourse/discourse-kanban-theme 📖 New to Discourse Themes? Beginner’s guide to using Discourse...
Now you can combine the horrible UX of Jira with the horrible performance of Discourse.
-
Is it possible to create a "topic deleted, user banned" category where to drag topics into?
-
@Zecc You mean some equivalent of "all topics"?
-
@Zecc said in Using Discourse as a mere bug tracker is for pussies!:
Is it possible to create a "topic deleted, user banned" category where to drag topics into?
That would really speed up Jeff's workflow, but he wouldn't be able to admit that someone on this forum had a good idea.
-
That would make it so easy to be a Wally. "I got no work done this week because clicking on my tickets resulted in a '504 OK Error'. When I reported the bug, I got banned from our tracker."
-
Lists are ‘lazy-loaded’, so performance is reasonable, even for very large numbers of categories.
Successsfully tested with TWO WHOLE CATEGORIES!!!
You can enter fullscreen mode for even more space to organise your projects:
But not on mobile, that's different
-
@izzion said in Using Discourse as a mere bug tracker is for pussies!:
But not on mobile, that's different
Nobody does project management on mobile. Project management is serious, and needs you to use a serious computer.
-
@dkf said in Using Discourse as a mere bug tracker is for pussies!:
@izzion said in Using Discourse as a mere bug tracker is for pussies!:
But not on mobile, that's different
Nobody does project management on mobile. Project management is serious, and needs you to use a serious computer.
It's so serious, you need a trio of quad-socket 1024GB RAM servers to host your Discourse all-in-one forum, ticket tracker, source code repository, furnace, and CPU thermal stress-tester for your team of 8 engineers and one manager.
-
@mott555 You forgot about the mailing list functionality
-
Discourse as bug reporting software would fly a lot smoother if it had GitHub-issues-style interface. Why not invest the time spent making this into the use of the software that's actually used?
-
@DoctorJones said in Using Discourse as a mere bug tracker is for pussies!:
Now you can combine the horrible UX of Jira with the horrible performance of Discourse.
APOLOGIZE TO JIRA!
Seriously, I've never understood most of the Jira complaints around here.
-
@boomzilla The main horrible thing I have to deal with whenever I have to deal with our jira is how slow it is.
All updates are mirrored to the legacy bug tracker, so I use that at every opportunity.
-
@PleegWat said in Using Discourse as a mere bug tracker is for pussies!:
The main horrible thing I have to deal with whenever I have to deal with our jira is how slow it is.
Sounds like a server provisioning problem to me. Ours is reasonably fast for things I'd expect to be reasonably fast (like, displaying all the thousands of tickets that have been assigned to me is slow, but showing recently updated stuff isn't).
-
@boomzilla said in Using Discourse as a mere bug tracker is for pussies!:
@DoctorJones said in Using Discourse as a mere bug tracker is for pussies!:
Now you can combine the horrible UX of Jira with the horrible performance of Discourse.
APOLOGIZE TO JIRA!
Seriously, I've never understood most of the Jira complaints around here.
I dislike the clumsy interface where things are hidden in popups an long menus, stuff that should be stock functionality but is sold as extra add-ons and so on.
On the other hand, I've never used a task management system I liked, and I've seen a lot worse than Jira.
I've also probably never seen a properly configured Jira, that might also be a part of my dislike of it.
Overall I find that naming it after a gigantic lizard-thing that shoots fire is pretty apt.
-
@Carnage said in Using Discourse as a mere bug tracker is for pussies!:
Overall I find that naming it after a gigantic lizard-thing that shoots fire is pretty apt.
My biggest complaint about it is people who pronounce it with a long
i.
-
@boomzilla
Isn't it "Jeer-uh", like how you jeer at people that are forced to work with it?
-
@boomzilla said in Using Discourse as a mere bug tracker is for pussies!:
displaying all the thousands of tickets that have been assigned to me
I do hope the majority has
Status: Closed
-
@Carnage said in Using Discourse as a mere bug tracker is for pussies!:
On the other hand, I've never used a task management system I liked, and I've seen a lot worse than Jira.
QFT
-
@AlexMedia The legacy bug tracker is awesome.
select bug_status, count(*) from all_bugs where programmer=usernameI'd tell you how long it took to return but I'm at home and the bug tracker is at work.
-
@boomzilla said in Using Discourse as a mere bug tracker is for pussies!:
@DoctorJones said in Using Discourse as a mere bug tracker is for pussies!:
Now you can combine the horrible UX of Jira with the horrible performance of Discourse.
APOLOGIZE TO JIRA!
Seriously, I've never understood most of the Jira complaints around here.
My main problem with it is it still feels like a bug tracker (its original purpose) that has had other workflow management stuff bolted onto it. I don't think it's bad, but it is annoying.
Edit: For example, why does Resolved make the item get strike-thru instead of when Closed? Ideally strike-thru should indicate completely done, not "done if this was a simple bug tracker".
-
@mikehurley said in Using Discourse as a mere bug tracker is for pussies!:
For example, why does Resolved make the item get strike-thru instead of when Closed?
Because it is supporting a complex issue management workflow where different parties have to sign off on different stages. Some people need that level of enterpriseyness, but it's utterly overblown for many other folks.
-
@PleegWat said in Using Discourse as a mere bug tracker is for pussies!:
@AlexMedia The legacy bug tracker is awesome.
select bug_status, count(*) from all_bugs where programmer=usernameI'd tell you how long it took to return but I'm at home and the bug tracker is at work.
ORA-00979: not a GROUP BY expression
-
@mikehurley said in Using Discourse as a mere bug tracker is for pussies!:
@boomzilla said in Using Discourse as a mere bug tracker is for pussies!:
@DoctorJones said in Using Discourse as a mere bug tracker is for pussies!:
Now you can combine the horrible UX of Jira with the horrible performance of Discourse.
APOLOGIZE TO JIRA!
Seriously, I've never understood most of the Jira complaints around here.
My main problem with it is it still feels like a bug tracker (its original purpose) that has had other workflow management stuff bolted onto it. I don't think it's bad, but it is annoying.
Edit: For example, why does Resolved make the item get strike-thru instead of when Closed? Ideally strike-thru should indicate completely done, not "done if this was a simple bug tracker".
The strike-through stuff is something which can be configured in the workflow management stuff if you know what to look for and are willing to migrate all the existing tickets.
No, the most irritating is that they're now redesigning the whole thing with a flat design full of whitespace and then are dropping all kinds of features while others were never implemented in the first place.
-
@boomzilla said in Using Discourse as a mere bug tracker is for pussies!:
displaying all the thousands of still open tickets that have been assigned to me is slow,
FTF
-
@dkf said in Using Discourse as a mere bug tracker is for pussies!:
@izzion said in Using Discourse as a mere bug tracker is for pussies!:
But not on mobile, that's different
Nobody does project management on mobile. Project management is serious, and needs you to use a serious computer.
-
@JBert said in Using Discourse as a mere bug tracker is for pussies!:
No, the most irritating is that they're now redesigning the whole thing with a flat design full of whitespace and then are dropping all kinds of features while others were never implemented in the first place.
Didn't know this was happening.
-
@boomzilla They sent me an email because I'm the admin of a JIRA Cloud instance.
You can read more about it here: https://confluence.atlassian.com/jirasoftwarecloud/work-in-the-new-issue-view-962349039.html
Of course, if you are using an on-premise JIRA then you might be able to escape the intial roll-out phase and hopefully get something which has been through some more rounds of feedback before they port it to JIRA Server edition. But if you are using the Cloud version, you have something to look forward to.
EDIT: They are also removing the modal
Editscreen and instead asking you to change fields one by one in the flat design. At least they are planning to make "summary" emails rather than sending one email for every fart in an issue.
-
@boomzilla said in Using Discourse as a mere bug tracker is for pussies!:
@PleegWat said in Using Discourse as a mere bug tracker is for pussies!:
The main horrible thing I have to deal with whenever I have to deal with
our jirait is how slow it is.Sounds like a server provisioning problem to me.
The edited version is how I read the post at first. Of course "it" then refers to the software mentioned in the topic. I then wondered who stole your username (or alts leaking etc.).
-
@JBert said in Using Discourse as a mere bug tracker is for pussies!:
You can read more about it here: https://confluence.atlassian.com/jirasoftwarecloud/work-in-the-new-issue-view-962349039.html
It does not look bad to me. It is also not too flat—most buttons do still look like buttons and not just any label.
@JBert said in Using Discourse as a mere bug tracker is for pussies!:
EDIT: They are also removing the modal Edit screen and instead asking you to change fields one by one in the flat design.
As long as they make all fields editable, that's improvement too. In the current state you can edit some fields separately, but not all, so you notice something is wrong, click it to edit it, find it does not work, click Edit, and go hunting for the field again. The worst part of the UI, really. Good they are changing it.
-
@boomzilla said in Using Discourse as a mere bug tracker is for pussies!:
@DoctorJones said in Using Discourse as a mere bug tracker is for pussies!:
Now you can combine the horrible UX of Jira with the horrible performance of Discourse.
APOLOGIZE TO JIRA!
Seriously, I've never understood most of the Jira complaints around here.
3 different UIs to view the same user story. Some show the field I'm looking for and some don't, it's usually in the last one I search.
Maybe it's a customization fault, and that's why I hate customizable stuff.
-
@sockpuppet7 said in Using Discourse as a mere bug tracker is for pussies!:
it's usually in the last one I search
Well yes. Who keeps on looking for something after finding it?
-
@dkf said in Using Discourse as a mere bug tracker is for pussies!:
@sockpuppet7 said in Using Discourse as a mere bug tracker is for pussies!:
it's usually in the last one I search
Well yes. Who keeps on looking for something after finding it?
You may be surprised...
-
@pie_flavor said in Using Discourse as a mere bug tracker is for pussies!:
Discourse as bug reporting software would fly a lot smoother if it had GitHub-issues-style interface. Why not invest the time spent making this into
the use of the software that's actually usedliterally anything else, because burning your scrotum with a blowtorch would be a more productive use of your time?
-
@Polygeekery said in Using Discourse as a mere bug tracker is for pussies!:
burning your scrotum with a blowtorch
taking the pyro thing to a next level uh?
-
@sockpuppet7 said in Using Discourse as a mere bug tracker is for pussies!:
3 different UIs to view the same user story.
That's why I say it's only for better if the Edit one is going away. The other two—full size and side-bar in the backlog and kanban views—are almost the same except some of the buttons, unfortunately. If you have a more different view, that would then be customization.
-
-
@JBert said in Using Discourse as a mere bug tracker is for pussies!:
@boomzilla They sent me an email because I'm the admin of a JIRA Cloud instance.
You can read more about it here: https://confluence.atlassian.com/jirasoftwarecloud/work-in-the-new-issue-view-962349039.html
Of course, if you are using an on-premise JIRA then you might be able to escape the intial roll-out phase and hopefully get something which has been through some more rounds of feedback before they port it to JIRA Server edition. But if you are using the Cloud version, you have something to look forward to.
Yeah, we are on premises, so hopefully.
EDIT: They are also removing the modal
Editscreen and instead asking you to change fields one by one in the flat design.Honestly, I only use the edit screen when they've hidden empty fields.
At least they are planning to make "summary" emails rather than sending one email for every fart in an issue.
-
@boomzilla said in Using Discourse as a mere bug tracker is for pussies!:
APOLOGIZE TO JIRA!
<grumble>Sorry Jira.</grumble>
*kicks Jira when @boomzilla isn't looking*
@boomzilla said in Using Discourse as a mere bug tracker is for pussies!:
I've never understood most of the Jira complaints around here.
Jira is fine until someone asks you to customise any of it to suit your team.
@Carnage said in Using Discourse as a mere bug tracker is for pussies!:
I dislike the clumsy interface
This
My main problem with it is this, whenever I come to do anything with Jira, they've seemingly changed the fucking UI yet again. If I ever google for how to do something, the only solutions I find were applicable to Jira several versions ago.
They seem to bikeshed more than Jeff et al.
@JBert said in Using Discourse as a mere bug tracker is for pussies!:
they're now redesigning the whole thing
I rest my case, your honour.
-
@Polygeekery said in Using Discourse as a mere bug tracker is for pussies!:
literally anything else, because burning your scrotum with a blowtorch would be a more productive use of your time
@Luhmann said in Using Discourse as a mere bug tracker is for pussies!:
taking the pyro thing to a next level uh?
Giving new meaning to the word "fireball".
-
@Luhmann said in Using Discourse as a mere bug tracker is for pussies!:
@Polygeekery said in Using Discourse as a mere bug tracker is for pussies!:
burning your scrotum with a blowtorch
taking the pyro thing to a next level uh?
This is not a thing, as far as I'm aware, but it wouldn't surprise me if it was.
Fire play and fire cupping are real things I have seen.
-
Something which I really like about JIRA: JQL. Being able to search for issues by writing a SQL-like query is something which I like, as I get it. I prefer JQL over the clumsy "Expression builder" interface given to you by Azure DevOps.
Something I dislike about JIRA: how inconsistent it can be at times. Buttons that are available in one view but not in the other, for example. Sometimes this is due to customisation, but I do feel that the product should guide you when you customise it.
For example, if you add a custom field - the system should ask you "Where do you want this to appear?" and not leave it entirely up to the user (who more often than not might be a PMO who's just implementing a process) to figure out how the system should guide its users.
One of my pet peeves of a JIRA implementation I had to use for two years was the 'Story points' field: it only existed in the list view quick edit pane. When viewing the details of a story, the story points weren't visible. It wasn't visible on the detailed Edit page either. Only in the quick edit pane.
-
@AlexMedia said in Using Discourse as a mere bug tracker is for pussies!:
Something which I really like about JIRA: JQL. Being able to search for issues by writing a SQL-like query is something which I like, as I get it. I prefer JQL over the clumsy "Expression builder" interface given to you by Azure DevOps.
Seconded. I always fail to read the And / Or expressions with that expression builder whereas SQL / JQL just uses parentheses to group statements.
