Feature request to add issue-properties write to Atlassian MCP server

[Eleni Konior]

We're looking for a simple way to handle writes to issue properties through the Atlassian MCP server. The alternatives require a lot of overhead to avoid per-developer setup (e.g., Jira API tokens). Our engineers already heavily use the Atlassian MCP server (thank you!), so we're hoping to add one more tool or a wrapper tool that can handle various API operations perhaps?

We're also open to contributing to the repo: https://github.com/atlassian/atlassian-mcp-server but would want to know if this aligns with the team's (Atlassian's) roadmap. I don't see anything in the GitHub issues referencing issue properties.

[Tomislav Tobijas · Accepted solution]

Hi @Eleni Konior ,

There's no official/public roadmap when it comes to MCP development. I've looked for a bit in JAC if there are any mentions of using issue/work item properties, but nothing did pop out. 👀

I'm guessing you've tried using methods and endpoints related to Issue properties and that this isn't supported with MCP? (I haven't tested that part, so that's why I'm asking) 🤔

Meanwhile, you or your app admin can probably reach out to Atlassian Support to see if they will provide some additional insights that could be related to your requirements.

Btw, I'm going to move this to the Rovo forum group - someone might chime in with some additional info.
Also, when talking about MCP, there's a dedicated forum discussion group related to that: Atlassian Rovo MCP Server 

Cheers,
Tobi

[Eleni Konior]

Hi @TOB ! Thanks for the response

Yes, we've used the endpoints related to issue properties you linked above, which is not supported with MCP. For some context, we've built a skill that spawns a subagent at various points of its workflow to assign issue properties to a ticket. To get this working, we required all the engineers at our company to create a Jira API token and set that in their environment. This is a friction point, however, and it would actually be faster for us to work on extending MCP for this purpose than to remove the friction point a different way on our end.

Thanks for moving to the forum group! I'll reach out to support while I wait for others in the community to chime in.

[Tomislav Tobijas]

Thanks for the additional context @Eleni Konior!

I can share any updates/news if I stumble upon them 👀

Apart from everything stated above, you could maybe try using the in-app feedback option (through Rovo Chat, for example).

Again, this is general Rovo feedback, but the product team should redirect this to the appropriate internal team(s).

[Eleni Konior]

Awesome just sent that over with the link to this Community page as well as a GitHub issue I created: https://github.com/atlassian/atlassian-mcp-server/issues/142 

Thanks again  @Tomislav Tobijas !

[Dr Valeri Colon _Connect Centric_]

I do enjoy a good screenshot! Thanks @Tomislav Tobijas This still looks like a real gap rather than missing config. Atlassian’s MCP docs now support read/write operations in general, but I’m not seeing issue properties documented as an exposed MCP capability yet. So your GitHub issue + feedback path makes sense, and today this still looks like a feature request rather than something you missed in setup.

[Suyash Kumar Tiwari]

Hi @Eleni Konior  - Jira MCP PM here. Can you elaborate on your ask around the scenarios that you are trying to accomplish via MCP here? I get the ovearall picture, but a few real examples would help us create the right tooling with permissioning/scoping in mind. We are actively looking into it. 

[Eleni Konior]

Hi Suyash! Thanks for commenting and also on the GitHub issue.

We've been building a suite of agent skills for engineers to use so that we can get metrics on how agentic the org is. We've been using Jira issue properties via REST API to populate some of these AI metrics for how long it took to do a certain part of a task (e.g., a plan for the work item, the actual implementation of it, etc.). We've been using labels as well for rough time estimates, but the agents routinely make up labels they want to apply even though we have scripts in our skills that tell them what to do.

Cutting over fully to issue properties would avoid people gaming the system to appear in our metrics because they cannot apply changes via the UI like they can with labels. Using the MCP instead of the Jira REST API gives our users a better experience with less friction since now we ask them to create their own token with the relevant scopes applied.

So if the MCP had the ability to modify issue properties we'd be able to remove a lot of the work we've had to maintain in the skills repo as well as improve the experience of using the skills.