For the internal communication without our organization we're trying to setup a power automate flow to get the data from a microsoft forms form and create a issue in jira.
Using a Jira connector for Power-Automate we're able to create a issue but we're unable to add attachments to that issue.
We've created a Power-Automate flow that follows the following steps:
When a response is submitted, This is the trigger. When a response is submitted to the form the power automate flow will trigger.
Initialize a variable.
In order to add multiple attachments to a issue we're creating a array called aAttachments.
Apply to each loop.
Get response details from form
Create jira issue
Get attachments from form
Insert attachments in a json object.
loop trough all the entries in the json
Get file contents
Add file to array
HTTP Post request. Communicatie with the jira rest API and trying to send the file information.
All steps work apart from step 11. We keep getting a 404 return with the following output.
Issue doesnt exist or you dont have the right permissions to view the issue.
We know the issue exists because the issue is created, and the persmissions needed are open to the public.
This is the Post request:
What should change in order to add the attachments to the issue created.
This may help:
Issue attachments not getting through for non-admin users via email
1 - Navigate to the project where the issues are being created > Project Settings > Permissions and check if the user that is creating the issue (Or the default reporter set for your e-mail handler) is configured with the Create Attachments permission.
2 - Check if the attachment you are trying to add has the size allowed in your site, under Jira Settings > System > Attachments
Unable to attach files to issues in Jira
Related
I want to raise jira incident with approvers using rest api. I am unable to do so as i am getting below error:
customfield_XXXXX can not be set. it is not on the appropriate screen
I assume I can not add approvers while creating incident. I am using curl to raise incident.
If I try to manually create an incident, I don't get any options to add approvers, but once jira is created, I can see the option to update approvers manually from web ui.
Is there a way I can update an already raised incident with the correct approver name?
The Jira version we are using is v8.5.5.
The reason you cannot add approvers when creating the issue is that the approvers field does not exists on the screen which assigned to the create context of the screen scheme which is assigned to the incident issue type in the project's issue type screen scheme.
You are probably able to add approvers once the issue is created either because the field exists on the screen assigned to the edit context of the screen scheme, or because you are setting it on a screen during a workflow transition.
If you have site administration permissions (or maybe just project administration permissions depending on how the site is configured), and it makes sense in the context of your use case, you could add the approvers field to the create screen.
To update the field after the issue has already been created, without making any config changes, is dependent on how you are currently able to set the field. You will either be able to make an API request to directly update the field, or you will need to transition the issue through whatever transition currently allows you to set the field, again via API.
I have 2 instances of JIRA . I have written a script where tickets from one instance are read and a replicas of same are created in another instance.
Now the problem is , whenever I run the script it is generating duplicate tickets again and again.
How do I prevent this duplication of tickets? Please help.
Ideas:
Create a link field in each Jira issue and populate it. If the field is populated the script should not create a new issue
Use a "last synced" field in the source Jira and only create a new issue if the source issue has not been synced
You don't say but I assumed that this is a one way sync
How to get added Statuses on report creation in Jira Service Desk?
I added new issue status in Jira Statuses list and i want to access these added statuses list on Report Creation but I'm not able to getting it.
And see following screenshot for more understanding...
Iam trying to get all the files committed against a JIRA issue. Iam using the following method to get the information
GET /rest/dev-status/1.0/issue/detail?issueId=&applicationType=bitbucket&dataType=pullrequest
The JSON returns all the commits but not full list of files committed. if i commit more than 5 files on a single commit, then only the first 5 files are listed in the JSON. anyways to get the full list of files?
The resource you are using is not part of the public rest API of Jira, so you there is no guarantees around the response you will receive from it. It is very much use at your own risk.
The current implementation limits itself to only fetching the first 5 files changed, if you require more that this you will need to do a call to Bitbucket etc and lookup the diffstat information yourself eg https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Busername%7D/%7Brepo_slug%7D/diffstat/%7Bspec%7D
I have created a Jenkins job to execute robot framework. The results[log.html and report.html] of the Jenkins are getting displayed properly.
Now I am using the email-ext plugin to send the log file as email content to the specified group of users, but the received email doesn't display the content and shows error as "Opening Robot Framework log failed" in the email.
I have set the email-ext plugin as follows:
I wish to send the robot results as email content, not as an attachment, I have tried various methods like Linux, shell scripting etc, but still, it doesn't work. How can the log.html email content can be sent to the email body?
You will not be able to just put the entire content of the robot log.html in an email because it contains javascript.
I've been looking into this the last few days as well and have come to see that using a groovy based template using the jenkins Email-ext plugin is the way to go. Googling for 'jenkins robot framework email template' shows a few hits and one that I'm planning to try and then modify to my liking was this one:
https://github.com/vladwa/robot-email-template
From this I found that we don't have access to all of the test info built in, so I wrote up some modifications to load the robot output.xml as an artifact to then be able to inject any data in that file into the html email report. Here's the gist of that:
https://gist.github.com/harbdog/070f0be66ebae343d6d11e57a6c6fc08
Here's what it looks like for example:
You have to configure publish robot framework test result <post build> and then use {ROBOT_REPORTLINK} in email content section