Unable to Assign Jira Story to Teams User & Add Custom Fields in UiPath Workflow

Help Studio
, ,
1

I am currently working on automating Jira story creation using Microsoft Teams messages. While I have successfully built the workflow, I am facing two challenges. First, I am unable to assign the created Jira story to the user who posted the message in the Teams channel. Second, I am not able to add custom fields, such as Story Points or Original Estimate, to the Jira issue. I would appreciate guidance on how to map the Teams message sender to the corresponding Jira user and correctly assign the issue. Additionally, I need help in configuring the workflow to include custom fields when creating the Jira story. Could you please provide insights or best practices to resolve these issues?

2

@Devyanshi_Joshi

Welcome to the community

From the message object you would have the sender email which can be passed to get jira user activity and then pass the oputput to assign user

Use additional fields property to add custom fields

The image is a note explaining that custom fields can be set using either the Additional Fields or the Custom Fields property, providing RPA developers with a choice of input parameters. (Captioned by AI)
The image is a note explaining that custom fields can be set using either the Additional Fields or the Custom Fields property, providing RPA developers with a choice of input parameters. (Captioned by AI)828×309 83.4 KB

Cheers

3

Hello, Devyanshi here
I hope you are doing well.
I am reaching out regarding an issue with my UiPath workflow. I successfully created an end-to-end workflow that was running perfectly on Tuesday, allowing me to automatically assign Jira stories. However, when I attempted to run the same workflow today, I encountered an error (please find the attached screenshot for reference).
Despite posting a channel message, the issue persists. Interestingly, I have another workflow with the same functionality, except for the assignee part, and it continues to run successfully. This suggests that the issue might be related specifically to the assignee functionality in my original workflow.
Since this workflow was thoroughly tested and used to create multiple Jira stories earlier, I am unsure why it is failing now. I would greatly appreciate your assistance in diagnosing and resolving this issue at your earliest convenience.
Looking forward to your guidance.
The error I am facing is here:

1 Like
4

@Devyanshi_Joshi

  1. Screenshot is not visible
  2. If its because of assign then check if you have any permission changes
  3. better to create a separate topic as this is opened for a different purpose. that way we can help better with proper segregation or multiple things would be clubbed…

cheers

5

Okay, I’ll create new one, and I have not worked on custom fields as I have priority on assignee fields.

6

@Devyanshi_Joshi

Did you happen to check the permissions?

Cheers