4 ms·
isn't the problem described in the jira ticket?
by tekno45 5y ago
isn't the problem described in the jira ticket?
- throw0101a 5y ago> isn't the problem described in the jira ticket? Yes/perhaps/maybe, but it's nice to (a) have it in front of you without having to change programs or context, and/or (b) have it summarized, as the ticket may have 'extraneous' stuff like a bunch of back-and-forth with the user/client/tester/etc.
- erik_seaberg 5y agoOrganizations ought to preserve tickets across migrations to new systems, but they don’t always. Only commits are forever.
- icedchai 5y agoExcept tons of orgs squash before merge (unfortunately, IMHO) so individual commits are pretty transitory. Doing “conventional commits” for all those smaller commits seems wasteful.
- terinjokes 5y agoThey often believe they'll never change ticket systems. Until they find out one morning IT didn't subscribe to the same ideology.
- luxurytent 5y agoNice to have the problem in line because I can search git history. Also no guarantees that the Jira ticket will be around as long as the code.
- Liquid_Fire 5y agoThe problem the commit is addressing might not be exactly the same as the problem in the JIRA ticket (e.g. you're solving a bigger problem than just what the JIRA describes, or there are multiple causes and this commit fixes only one of them, etc).