solution to inform the team which a bug/issue/task was fixed/completed on via CruiseControl.net



  • I have recently joined a new company and I am dragging them by the scruff of their neck into the 21st Century when it comes to development and testing processes. I have just introduced JIRA after battling with the damn awful TFS tracker they were using. My next step is automated building, via CruiseControl.net but that's a side story which only bare some help to what I need advice on here. Anyway, so to my question. I am looking for a solution to informing the test team which 'version/build' a bug/issue/task was fixed/completed on. Back in their old TFS days they had a free type textbox for this, and they would manually update a config setting with the latest 'version' number that they had put in the bug tracker. Now be default JIRA's versioning is more advanced (and rightly so) and you need a new version entry creating to achieve this, which I am not prepared to let happen as it will only end in tears and a whole world of pain. Without a build server and automated building of projects we have disjointed build numbers, as currently the projects are built on our local machines and deployed to staging (by the developers) which isn't an ideal situation, but that's what I have to work with for now. I could add a free type text field to the issue objects in jira, which we could use to enter a build number or low end version number, which would work fine, except the build numbers would be disjointed between machines. So some arbitrary manual version numbers would have to suffice instead. Has anyone got any better ideas on what could be done to fix this problem?



  • Sounds like a pretty awful situation. Below is my suggestions, First is the suggestion you gave, Secondly you could add a label field and that way at least your users get some autocomplete functionality that might alleviate some of the pain Thirdly you could add a multi-select, whereby you could always add version numbers and manage that yourself.


Log in to reply
 

Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2