It’s faster for our designer to change code than file a ticket
1–6 of 6 posts
Re: It’s faster for our designer to change code than file a ticket
#2[deleted]
Re: It’s faster for our designer to change code than file a ticket
#3[flagged]
Re: It’s faster for our designer to change code than file a ticket
#4False dichotomy (for the clicks, of course). Filing tickets is still part of the process for both QA and record keeping.
I think this company is simply discovering what many have already learned: Having designers who can’t code combined with a coding team that is too backlogged too work with the designer isn’t productive.
Having designers who can code (through whatever form that takes) makes more sense for smaller teams than having a designer who just files tickets that never get prioritized.
Re: It’s faster for our designer to change code than file a ticket
#5False dichotomy (for the clicks, of course). Filing tickets is still part of the process for both QA and record keeping. I think this company is simply discovering what many have already learned: Having designers who can’t code combined with a coding team that is too backlogged too work with the designer isn’t productive. Having designers who can code (through whatever form that takes) makes more sense for smaller te…
It sounds as if you regard the ticket syste, as taking over the role of the version control system, or do I misunderstand?
Re: It’s faster for our designer to change code than file a ticket
#6False dichotomy (for the clicks, of course). Filing tickets is still part of the process for both QA and record keeping. I think this company is simply discovering what many have already learned: Having designers who can’t code combined with a coding team that is too backlogged too work with the designer isn’t productive. Having designers who can code (through whatever form that takes) makes more sense for smaller te…
It sounds as if you regard the ticket syste, as taking over the role of the version control system, or do I misunderstand?
Not at all. Tickets are for more than engineers: They’re useful for QA to confirm the feature, documentation writers to ensure they document changes, support people to know that something they’ve been warning customers about is now fixed and so on.
Version control is for the code. Tickets are for features.