Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Feature Requests
 Jira issue navigation in Source Links
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

kenny
Junior Member

19 Posts

Posted - Jul 15 2018 :  9:59:45 PM  Show Profile  Reply with Quote
I notice that this new plug-in does not allow customization of the URL part, can this be supported in the next version?

For example, we have these comments in our code

// PRODUCT-1234


So on the Source Links page in Options dialog, PRODUCT is the keyword, and - is the suffix. However, the URL/Exe is disabled and display as:

https://mycompany.jira.com/browse/$(Value)

This is not working at all, it should be:

https://mycompany.jira.com/browse/PRODUCT-$(Value)

sean
Whole Tomato Software

USA
2817 Posts

Posted - Jul 15 2018 :  10:25:10 PM  Show Profile  Reply with Quote
Yes, it does seem that you should be able to change the URL. I think you would want:
https://mycompany.jira.com/browse/$(Keyword)-$(Value)
We'll get it in the next release: case=117783.

Edited by - sean on Jul 15 2018 10:25:28 PM
Go to Top of Page

sean
Whole Tomato Software

USA
2817 Posts

Posted - Jul 21 2018 :  6:32:29 PM  Show Profile  Reply with Quote
case=117783 is addressed in build 2283.1.

The configuration dialog for the Jira plugin has a new edit control where you can specify the project key.

Project key can be blank, in which case only $(Value) is passed to the server. This is the behavior of the initial version of the plugin.
For example:
link configuration project key: <blank>
link definition keyword: jira;bug
Example source comment: jira=J0001
Targeted url: myJira.myCompany.com/browse/J0001
Example source comment: bug=J0002
Targeted url: myJira.myCompany.com/browse/J0002

Project key can be $(Keyword) in which case the keyword match in the source link instance is passed to server. This is the default value.
For example:
link configuration project key: $(Keyword)
link definition keyword: jtp;jt2p
Example source comment: JTP-001
Targeted url: myJira.myCompany.com/browse/JTP-001
Example source comment: JT2P-003
Targeted url: myJira.myCompany.com/browse/JT2P-003

Finally, Project key can be any other value and should match the project key defined in the Jira project. Use this when the keyword used in comments no longer matches the project key defined in Jira.
For example:
link configuration project key: JTP
link definition keyword: oldkey;jtp
Example source comment: OldKey-001
Targeted url: myJira.myCompany.com/browse/JTP-001
Example source comment: JTP-002
Targeted url: myJira.myCompany.com/browse/JTP-002
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2019 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000