• Type: New Feature
• Resolution: Unresolved
• Priority: Major
• Component/s: jiratestresultreporter-plugin
• Labels:

  None
• Environment:

  Hide

  - Jenkins master OS: Windows Server 2012 R2 (x86)
  - Jenkins version: 2.46.3
  - JiraTestResultReporter plugin version: 2.0.3
  - Jenkins is being run directly and was installed via Windows Installer
  - The Windows slaves are primarily launched via JNLP. The slave agent may be running as a service.

  Show

  - Jenkins master OS: Windows Server 2012 R2 (x86) - Jenkins version: 2.46.3 - JiraTestResultReporter plugin version: 2.0.3 - Jenkins is being run directly and was installed via Windows Installer - The Windows slaves are primarily launched via JNLP. The slave agent may be running as a service.

[JENKINS-45141] Support multiple jira projects

Collapse comment: Brian Vandegriend added a comment - 2019-01-04 18:08

Brian Vandegriend added a comment - 2019-01-04 18:08

Hi - I would be interested in this feature as well.  We use one Jira project for the actual test development and a second for software bugs/feature issues.  Thus, a failure can be attributed to either a test issue or a software bug and thus we need the ability to link a test failure to one of several Jira projects.

I'm not familiar with the source code but it can be easily supported by supporting multiple items in the Project Key field and using the first one in that list for creating new issues against.

 

Expand comment: Brian Vandegriend added a comment - 2019-01-04 18:08

Brian Vandegriend added a comment - 2019-01-04 18:08 Hi - I would be interested in this feature as well.  We use one Jira project for the actual test development and a second for software bugs/feature issues.  Thus, a failure can be attributed to either a test issue or a software bug and thus we need the ability to link a test failure to one of several Jira projects. I'm not familiar with the source code but it can be easily supported by supporting multiple items in the Project Key field and using the first one in that list for creating new issues against.  

Collapse comment: keith added a comment - 2021-04-30 09:19

keith added a comment - 2021-04-30 09:19

zaikinpv andreituicu

I'd like to add that myself and my team need this feature. We primarily have two projects which need to be monitored - the one we develop and a project we are dependent on, which we log against and monitor. 

If it was possible to add in an additional project key or two, at least just for the linking of issues rather than for creation of issues. It would make this tool a lot more practical for us.

We typically create our own issues and link; so the creation can be left as is if the functionality is hard to implement.

Great tool, thank you for your contributions!

Expand comment: keith added a comment - 2021-04-30 09:19

keith added a comment - 2021-04-30 09:19 zaikinpv andreituicu I'd like to add that myself and my team need this feature. We primarily have two projects which need to be monitored - the one we develop and a project we are dependent on, which we log against and monitor.  If it was possible to add in an additional project key or two, at least just for the linking of issues rather than for creation of issues. It would make this tool a lot more practical for us. We typically create our own issues and link; so the creation can be left as is if the functionality is hard to implement. Great tool, thank you for your contributions!