Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-21766

Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • jira-plugin
    • None
    • Linux

    Description

      Need the Jenkins 'Create Issue type' plugin to be more dynamic / configurable to allow for different default jira issue type.

      Utilizing Jenkins Jira plugin version 1.39

      Currently, jenkins project will only create an issue type of 'Bug'. We need the default configurable to align with the issue types created in jira for the project. Ideally an Issue Type drop-down box.

      Attachments

        Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-31164 Issue Type must be selectable from fetched dropdown

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            cvecchione chris vecchione added a comment -

            To be more exact we would like the "issue.setType("1") call be configurable like the other fields: Project Key | description | summary | assignee within the following code:

            https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/JiraSession.java

            public RemoteIssue createIssue(String projectKey, String description, String assignee, RemoteComponent[] components, String summary) throws RemoteException

            { RemoteIssue issue = new RemoteIssue(); issue.setProject(projectKey.toUpperCase()); issue.setDescription(description); issue.setSummary(summary); issue.setAssignee(assignee); issue.setType("1"); issue.setComponents(components); RemoteIssue createdIssue; createdIssue = service.createIssue(token, issue); return createdIssue; }
            cvecchione chris vecchione added a comment - To be more exact we would like the "issue.setType("1") call be configurable like the other fields: Project Key | description | summary | assignee within the following code: https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/JiraSession.java public RemoteIssue createIssue(String projectKey, String description, String assignee, RemoteComponent[] components, String summary) throws RemoteException { RemoteIssue issue = new RemoteIssue(); issue.setProject(projectKey.toUpperCase()); issue.setDescription(description); issue.setSummary(summary); issue.setAssignee(assignee); issue.setType("1"); issue.setComponents(components); RemoteIssue createdIssue; createdIssue = service.createIssue(token, issue); return createdIssue; }
            cvecchione chris vecchione added a comment -

            Also (this should not need to be stated but in case): the 'Create jira issue' UI should add this new field ("Issue Type") allowing user input.

            cvecchione chris vecchione added a comment - Also (this should not need to be stated but in case): the 'Create jira issue' UI should add this new field ("Issue Type") allowing user input.
            warden Radek Antoniuk added a comment -

            This sounds like a nice improvement! Would you consider creating a pull-request with this implemented?

            warden Radek Antoniuk added a comment - This sounds like a nice improvement! Would you consider creating a pull-request with this implemented?

            People

              Unassigned Unassigned
              cvecchione chris vecchione
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: