News for hackers. Stuff that matters.

A comment on JIRA is an antipattern. Parent comment

Re:JIRA is an antipattern by bloomca on Sunday December 09, 2018 @03:30PM (#18643082)
I think it is possible only in simple software (when you are developing an MVP, or just early stages).

Complex tasks are incredibly hard to finish as a single ticket – with such granularity you might have opaque progress for couple days, and you hide a lot of details from everyone.

Unless you mean "tickets" as "user stories", they can be (although not always) treated like that.

[ Parent | on HN ]
Re:JIRA is an antipattern by captain_crabs on Sunday December 09, 2018 @04:18PM (#18643334)
God I can't stay away from this thread.

Yeah - entirely depends on your subdivision vernacular. Some people make subtasks in a ticket, some people make tickets linked to other tickets, some people do both and link those to "features" which are themselves tickets (like the environment I work in).

Just depends!

[ Parent | on HN ]
Re:JIRA is an antipattern by captain_crabs on Sunday December 09, 2018 @04:04PM (#18643267)
Sounds like we agree, but use different names for the same things and some of the same names for some different things! :)
[ Parent | on HN ]