nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to use JIRA API to change the transitioner of status as another user

Sughosh Kulkarni

I am using Python and JIRA API to change a status from To Do to In Progress.

The problem I am facing is that the transitioner is set to me because I am using my credentials. Is there a way to change the user to asignee?

I am using the below code in Python.

jira_session.transition_issue(issue, status)

# Issue is the Issue Key

# Status is a string containing the code for transition. Example: '151'

Accepted answers

All comments

Mohamed Benziane

Hi,

Welcome to the community.

No you can't, what you can do with the API is what you can do using the UI. So unless you change the account the transitioner will be you in this case.

So i don't know your use case but it sound like a bad practice.

Sughosh Kulkarni

Okay, thank you.

The use case is that we are updating the transition of status from python using the API. But the updates are coming out in my name.

The reporter gets an email stating that I transitioned the status to something ("resolved" for example)

I was wondering if there was a way to make the transition to be the assignee.

But anyway, thank you for your answer.

Mohamed Benziane

In this case, you could create a generic account, something like "jira_admin" that you will use in your python script.

Lakshmi Narasimha Murthy Annavajhula

Hi @Sughosh Kulkarni I am also trying to do the same. In my case I am trying to change the transition of the issue from backlog to resolved as part of testing but I couldn't do it there is an error stating as below. any help would be highly appreciated. Thanks

response text = {"errorMessages":["It seems that you have tried to perform a workflow operation (Resolve Issue) that is not valid for the current state of this issue (TOOLSENG-3701). The likely cause is that somebody has changed the issue recently, please look at the issue history for details."],"errors":{}}

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

transition

assignee

jira-service-management-cloud

jira-service-management