Rundeck JIRA plugin shows ticket not found error despite valid ticket ID

Other Questions Jira
1

I am running Rundeck community version 4.10.1 and trying to set up JIRA ticket validation in my workflows. I have installed the JIRA plugins and can see the “jira issue exists” step available in my workflow options.

My configuration in the project settings looks like this:

project.plugin.Notification.JIRA.login=myuser
project.plugin.Notification.JIRA.password=mypass  
project.plugin.Notification.JIRA.url=https://mycompany.atlassian.net

But when I run my job it fails with this error:

[Workflow result: , step failures: {1=JiraIssueNotFound: Issue key "ABC-123".}, status: failed]

Here is my job configuration:

<joblist>
  <job>
    <context>
      <options preserveOrder='true'>
        <option name='ticket_id'>
          <description>JIRA ticket to validate</description>
        </option>
      </options>
    </context>
    <defaultTab>nodes</defaultTab>
    <executionEnabled>true</executionEnabled>
    <id>12abc34-d567-89ef-gh01-23456ijklmno</id>
    <loglevel>INFO</loglevel>
    <name>validate jira ticket</name>
    <sequence keepgoing='false' strategy='node-first'>
      <command>
        <step-plugin type='JIRA-Issue-Exists'>
          <configuration>
            <entry key='issue-key' value='${option.ticket_id}' />
          </configuration>
        </step-plugin>
      </command>
      <command>
        <exec>echo Ticket validation passed</exec>
      </command>
    </sequence>
  </job>
</joblist>

The ticket definitely exists in JIRA. I am using the Jira Notification plugin version 1.0.1 installed through the Rundeck web interface. What could be causing this issue?

2

Your JIRA Notification plugin 1.0.1 is the problem. That version’s ancient and doesn’t play nice with Rundeck 4.10.1. I hit this same issue last year during our upgrade - the plugin fails silently even when everything looks configured right. Upgrade to a newer JIRA plugin version or grab one of the community alternatives. Also flip your Rundeck logs to debug mode and check for SSL cert errors or connection timeouts. The real error usually hides in the system logs while your job just spits out that useless “ticket not found” message.

3

check your jira url config - i had this same error bc i was missing the /rest/api/2 endpoint in my connection settings. also make sure your user has the right project permissions. sometimes rundeck can’t see tickets even when they exist if ur missing browse project permissions.

4

Had the same problem - it’s usually an auth issue. You’re using basic username/password, but if you’re on Atlassian Cloud, you need an API token instead of your regular password. Generate one in your Atlassian account settings and swap it for the password field. Also check that your account can actually view the project where ABC-123 lives. Double-check your ticket ID format too - no extra spaces or weird characters. The plugin’s picky about auth and permissions even when you can see the ticket fine in the browser.