Flyspray - The bug killer!

  • Status Planned
  • Percent Complete
  • Task Type Feature Request
  • Category Backend/Core
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version
  • Due in Version 2.0
  • Due Date Undecided
  • Votes 2
    • kosnik (01.03.2019)
    • H (12.08.2015)
  • Private
Attached to Project: Flyspray - The bug killer!
Opened by Jordan Mendler - 17.01.2013
Last edited by peterdd - 12.08.2015

FS#1818 - Git/SVN/CVS Integration

Should be able to reference a ticket # when committing code, and then have a way to input your repository path to flyspray, and let it search all your commits for ticket #'s. Then should parse it, and have a link to that commit within the ticket.

Jordan Mendler commented on 17.01.2013 11:52

Similarly should be able to do it backwards – in flyspray have a field called commit where can add an affected commit from Git, SVN, etc and then it will link it.

Project Manager
Psychokiller1888 commented on 06.03.2015 22:29

Yeah, your second idea is very doable, the first one bit harder. Both are needed imo

H commented on 12.08.2015 07:09

I don't know how easy the flyspray api is to use. But I think part can be easily implemented using a git hook that scans the commit message and then adds a comment to an issue if a reference is found.

H commented on 12.08.2015 07:10

Higher priority please.

Project Manager
peterdd commented on 12.08.2015 07:10

Good candit for a 'plugin'.

The way referencing a github commit in a flyspray task or comment(bug?) can be done yet (in a simple way) by using the 'Add a link' feature.

Should not be implemented hardcoded into flyspray or at least should be done in a way to move it later easy to a plugin/extension if flyspray one day really gets a plugin system.

Questions popping up:

  • permissions,
  • enable/disable per flyspray installation or per flyspray project
  • how to avoid spam from the external sites


Available keyboard shortcuts


Task Details

Task Editing