Bugzilla – Full Text Bug Listing
| Summary: | Allow pluggable strategies to resolve issue urls from VCS comments | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Eugene Kuleshov <ekuleshov> | ||||
| Component: | Mylyn | Assignee: | Eugene Kuleshov <ekuleshov> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P4 | CC: | steffen.pingel | ||||
| Version: | unspecified | Keywords: | helpwanted | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 145214 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Eugene Kuleshov
Created attachment 46447 [details]
Example of CVS comments in sync view
Example of CVS comments in sync view used by Spring team. Note Jira issue numbers referenced up there.
I'm thinking that for now we 'require' that there be some prefix before the task's key. For JIRA I've made the prefix be "issue SPR-2227". While this has the benefit of being clear and consistent without much overhead, the cost of is that we do't correctly hyperlink reports from committers not using this convention, and in some cases it is be possible to resolve those (e.g. the first part of every project, e.g. "SPR-" on a JIRA server could be cached locally). Not likely we'll have time to do the latter for 1.0 so marking as helpwanted. Mik, requiring "issue" prefix for Jira would be a huge limitation. I can't possible tell somebody whom project I monitor how his comments should look like. So what you're saying is that seeing just the issue ID alone is a common occurrence? I'm not sure if we have all of the project prefixes from JIRA Core Services or if it's even something that JIRA exposes. If it does this should be doable, and the extensible matching seems like a good idea so I'm tentatively scheduling this for 1.0. But since it's not clear that we'll be able to prioritize it I'm leaving it as 'helpwanted' for now. (In reply to comment #4) > So what you're saying is that seeing just the issue ID alone is a common > occurrence? I'd say so. > I'm not sure if we have all of the project prefixes from JIRA Core > Services or if it's even something that JIRA exposes. It does: JiraServer jiraServer = JiraServerFacade.getDefault().getJiraServer(repository); Project[] projects = jiraServer.getProjects(); ... project[i].getKey(); ... project[i].getUrl(); Deferring, although Eugene, you may have made some progress on this already with ILinkedTaskInfo? (In reply to comment #6) > Deferring, although Eugene, you may have made some progress on this already > with ILinkedTaskInfo? Yep. It is "accidentally" fixed. JiraRepositoryConnector.getTaskIdsFromComment() provide custom strategy to parse repository-specific links. That is what original report was requesting. So, I basically ended up implementing it myself... I suspected that :) |