Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • +1 for bug fixes but what about new features? Unless new features are all created in JIRA as well... Commented Oct 6, 2011 at 9:45
  • 4
    @Sardathrion - Personally I'd create trackers for the new functionality in JIRA. We do this with Bugzilla and it gives the test team (and everyone else) good visibility of everything being put into a release and minimises things going out when they've not been tested / code reviewed / whatever. Commented Oct 6, 2011 at 12:46
  • @JonHopkins: While a bug tracker can be used for new features, it may not be the ideal tool. Of course, your mileage shall vary ^_~ Commented Oct 6, 2011 at 12:59
  • 4
    I came to love having a ticket assigned to every commit (some tickets can easly have multiple commits, of course): it's a very simple way to get more background information when inspecting code later on. "Why did they do that?" is much easier to answer when you have the commit comment and an issue tracking entry. Commented Oct 6, 2011 at 14:19
  • 1
    Sure - and once you've gotten it reviewed, you can merge to master.. whereby the ticket reference in the branch name is lost but not if it was also in the commit message. Commented Dec 27, 2013 at 12:35