[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Feature request: beeter issue tracker integration in history dialog

From: Friedrich Brunzema <brunzefb_at_yahoo.com>
Date: Sat, 1 Jun 2013 08:30:32 -0700 (PDT)

> It would be great to add the ability to use issue tracker integration plugins in history dialog. For example, this can be used to display issue information such as full title, status and the person, responsible for on hover on the issue's number.

What if just hovering on the link to get information proves impractical to implement - what would then be your next preferred use case? Just assume your desired functionality is already in Tortoise and explain how things would work step by step with sufficient detail. What bug/issue tracking system do you use? Does your issue tracking system have the capability of displaying your issue by Shell-Executing a URL?

In my company we use the Atlassian Jira tracking system; issues are in the format CL-3423 (two capital letters indicating a JIRA project, followed by a dash, followed by a bunch of digits(issue number). We have multiple projects, although people tend to work in a single one. A regular expression could be used find this issue-number text, one could then create a hyperlink such as http://myissuetracker.com/browse/CL-3423?jql=. To implement this in a somewhat generic way, one would need at least two configuration items, the regular expression to find the issue, as well as the URL to the issue tracker with a tag indicating where to substitute the issue number.

Use Case 1 (Searching)
1. User brings up Log Dialog
2. User types an search term containing text previously configured to indicate that this is an issue tracker link. User possibly uses a special search syntax, such as issue:CL-3423
3. The system searches and highlights (hyperlinks) found issues in the middle window which shows check-in comments. System has transformed any matched issue text into a hyperlink(s).
4. User clicks on a hyperlink.
5. Browser opens the issue in the issue tracking system. User may have to log-in to the issue tracker before being able to see the issue.

Use Case 2 (Configuring)
... (need to define this) ...

Would you be willing to help implement something like this? If you can't code, do you know of someone who can and would help, or are you able to help in other ways (beta testing, writing documentation etc). But before even thinking about the implementation, we need consensus on what a good use case is.


Friedrich Brunzema


To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-06-01 17:30:34 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.