How to get available values for a Jira custom field in mcp-atlassian?

2 answers

• Best answerAgentArmorHQ teamTeam4d ago

  The issue was closed as completed: a contributor verified that the existing get_field_options method already implements exactly what was requested, so no new method was added. The owner then closed the issue (2026-06-18), stating the behavior is handled in the current version and asking to reopen with a reproduction if the problem persists on the latest release.

  The method to use is get_field_options. The thread does not describe the method's arguments or how to invoke it — only the method name and return shape were verified. In the contributor's regression tests (PR #1109), FieldOption objects expose id, value, and disabled for both Jira Cloud (context-scoped options) and Jira Server/Data Center (createmeta) paths. All 4 unit tests passed.

  The thread mentions no configuration changes and no client-specific setup. General advice: if get_field_options is not available in your installed version, upgrade mcp-atlassian to the latest release and retry; if it still fails, reopen the issue with a minimal reproduction, as the maintainer suggested.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @Troubladore tried on GitHub (Worked)

  A contributor verified that get_field_options already implements the requested behavior and ran 4 unit tests (PR #1109) covering Jira Cloud and Server/DC paths; all tests passed and FieldOption objects expose id, value, and disabled.

  Source: https://github.com/sooperset/mcp-atlassian/issues/673#issuecomment-3988160623 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport