Home → Suggestions →

Subject: Links from and to Lighthouse tickets

Original Post

David Zuelke

08 Feb, 2010 06:53 PM via web

Admin Functions

• Edit
• Remove/Spam

After setting up Lighthouse integration, I did a commit with [#123 state:resolved], which worked as expected, except for two caveats:
1) that part of the commit message does not show up in Beanstalk, which also means I can't click it to go to the Lighthouse ticket from inside Beanstalk. Very bad. What's the point of having this integration if I can't jump to a ticket from the timeline view in Beanstalk?
2) inside the Lighthouse ticket update made by Beanstalk, there is no link to the commit in Beanstalk. Same issue as above... I can't quickly jump to associated changesets from a ticket.

Can you please fix this? The current solution seems to miss the entire point of an integration between issue tracking and version control... my life is made easier by being able to cross-reference tickets and commits, not by being able to mark a ticket as closed from within the SVN commit message. Look at Trac as an example of how it's done in an awesome way, you can even hover changeset IDs in ticket comments to see the commit messages, or the ticket number in changesets to see the ticket summary. http://trac.agavi.org/ does this well, and it makes for excellent accountability/traceability, because people immediately see the benefit of always referencing tickets in commits.

1. Support Staff 2 Posted by Igor Baloš on 08 Feb, 2010 07:16 PM

   

   Hi David,

   thank you for using Beanstalk. Let me try to answer both questions:

   1) In Beanstalk we hide tags which are used for integrations. The reason we do this is to keep the commit messages in your beanstalk accounts clean and readable. We are trying always to keep it clean, nice and easy to use. Since there are different integrations options we want the commits to look good for all of them. However we will discuss this with the team.

   2) In Lighthouse indeed there is no link back to beanstalk changesets. I will contact our developers to see to implement this in near future.

   Thanks
   Igor Balos
   QA Lead
   http://twitter.com/ibalosh
   

   Admin Functions

   • Edit
   • Remove/Spam

2. 3 Posted by David Zuelke on 08 Feb, 2010 10:24 PM

   

   Igor,

   thanks for the quick feedback.

   I understand you want it to look nice and clean, but I'd argue that it's not easy to use if
   a) the commit message I see in svn log et al differs from what I see in Beanstalk (maybe not hiding those parts could be a "power user" option?)
   b) the enabled integration doesn't work in both directions... you don't even have to show the full tag (although I guess that would be good) in order to link to the ticket!

   I've worked this way for a very, very long time, and it's simply great because you don't lose track of things. If you look at a commit, then the corresponding knowledge (why was that change made? what other commits are related to this? who decided this?) are right at your fingertips if you can jump to the ticket, and the ticket gives you a comprehensive overview of all changes that were necessary to fix the defect (or implement the feature or whatever the ticket type was).

   An example: if you look at http://trac.agavi.org/changeset/4354 you can jump right to http://trac.agavi.org/ticket/1183 where you see why the change was made, what steps were taken to get to this decision, and that changeset http://trac.agavi.org/changeset/4355 for ticket http://trac.agavi.org/ticket/1185 is related to the issue. And that is important, because if someone does svn blame on the changed file because he thinks that a certain line of code is stupid, he'll see these details, and he then has all the necessary knowledge to make an informed decision on how to move forward.

   Admin Functions

   • Edit
   • Remove/Spam

3. Support Staff 4 Posted by Igor Baloš on 09 Feb, 2010 09:54 AM

   

   Hi David,

   thanks for the feedback, this makes sense. We will review the integrations with the team and see if it's possible to add this feature too in near future.

   Thanks
   Igor Balos
   QA Lead
   http://twitter.com/ibalosh

   Admin Functions

   • Edit
   • Remove/Spam

4. Support Staff 5 Posted by Igor Baloš on 10 Mar, 2010 02:20 PM

   

   Hi David,

   we added links from Lighthouse back to Beanstalk. Now when you do a commit, link to Beanstalk changeset will appear in Lighthouse changeset and in task which you managed with the commit message.

   Igor Balos
   QA Lead
   http://twitter.com/ibalosh

   Admin Functions

   • Edit
   • Remove/Spam

Comments are currently closed for this discussion. You can start a new one.