Prince Nyeche - ELFAPP Atlassian Partner

I think the PAT requires just your username and not your email address if it works as Bearer. Just a hunch given the tests you've done.

There seems to be some form of error with your query that why it shows 400 being a client error. When such error occurs it could literally mean you do not have permission to probably browse certain issues that such field returns. Probably worth checking the permissions or project configuration to be certain.

The format for custom fields of certain field types are mentioned here

I don't think its possible to do such. Adding watchers to the watchers field is a Jira feature and customer only accounts (added on organizations) cannot be added as a Jira user. Therefore, you can't add such user into that field. What you should do here is allow the ability to share a ticket if it is not already enabled…

Your URL is not formatted properly and when you click on it or paste it on your browser it becomes a malfunctioned URL. Make sure that there's no newline on the URL string which might be causing the problem.

Hey folks, Sorry for the lengthy time it took to post a response. I have been busy with a lot of other projects I'm working on and haven't had sufficient time to look into this issue properly. I'm currently only running maintenance updates (i.e. bug and security fixes if any) that may arise on the app. There are some…

Hey @Doug Levitt You will need to script everything which includes multiple functions that processes request or listens for events. ScriptRunner uses groovy script and part of making it work for you would be to know how to code extensively in groovy. As long as you can do that, you can create your own functions and work…

You can always create an automation that sends a web request to JSM API to fetch the organization id available and append the value to a custom field.

--data '{"fields": {"project":{"id": "18500"}, "customfield_16600": {"id":"19302", "value": "$name1"}}}' Do you see the single quote before the curly bracket, you're suppose to have that. 

You can't embed issue collectors on cloud instances because you can't inject scripts or codes into cloud instance. So it is meant to be embedded on other web apps or website (which you have control over) and triggers an issue creation to the connected Jira project instance.

Hey @Miguel Angel Velazquez Solis It's suppose to try to convert that using utf-8 character encoding as that's the default on unix-like systems. However, I think if you're using windows this has to be explicitly mentioned when writing to a file. I'll push an update about this problem. Please can you create an issue…

If you're using this snippet from the command line, isn't your data argument value suppose to be wrapped in single quotes? --data '{"fields": }'

Jira doesn't block attachments by mimetypes. As an alternative, you could probably create an automation externally that would check periodically for attachments on an issue and if it detects mimetypes that is not accepted, it deletes it. 

It mentions "Returns a list of all statuses associated with active workflows." So the statuses has got to have been used in an active workflow within your instance. Basically it should return all the global statuses as well as those used by team-managed projects.

You should look into Jira Service Management server REST API if you're using a self-hosted version of Jira and if your use case can't be achieved by Jira's native features.Also, if you want to create a user feedback system, why not use Issue collectors or JSM Widgets which are practically existing feature within the…

If you can, you should script the solution or probably contact an Atlassian partner who can do custom development. The latter being the fastest way to get your solution.

Depending on what the user is intended for, you can either use one that would connect to multiple integration or use one user per each integration you want to connect to.

Simply navigate to your admin hub https://admin.atlassian.com and select the organization you want this user to be in (i.e if you have multiple organizations) then invite a user that you want to use as an automated user. See details here

On Jira cloud you will need a license user if you want to use it as an automated bot user. There's nothing like a service user account which are not billed or licensed. So start first by creating a license user account which you can then use as an automated user account in your codes or integration.

You need to extract the content of the HTML page. This is not something you would easily do on a command line in shell. You will need to properly script a solution using a HTML parser (probably in python) and get the content of each column within the confluence page content of that table. Then you can translate the output…

You should definitely look into the Jira python library if you really want to write a logic for your use case. As that would give you a head start in your scripting option.

That should be referring to the serviceDeskId. That information is contained there in the request payload. So you have to use a combination of identifying the request type by name, then use the serviceDeskId to perform the change. It's the same way automation for Jira does it.

How about giving the objects the hierarchy you want by mutating it. I know from the example server don't have it but you can always design your app to preconfigure the hierarchy by instructing the user to mention which issue type is higher than the other. i.e You can setup a configure issue type screen that will just show…

That's even better because they are particularly similar in most aspect. Were you able to get this issue resolved with those information @Bruno Mesquita dos Santos?

First of all, do you know how to code in groovy? If you don't then it would be difficult to explain the concept. However, what you should do is look for similar examples here https://library.adaptavist.com/ If you do then, the endpoint you should focus on is the get all request type.Please note that the API is…

You should look into Jira software endpoint if you're specifically looking into boards https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-issue-get If you can get the issues on a board, you can retrieve the board id and use that to query for the specific board details…

Basically, you will need to iterate over a list of files or in this case if you're uploading from a directory. You can to walk through the directory to upload the attachments per issue key or issue keys. However, if these attachments exist on a different Jira platform. You can look into this post and use a similar solution.

It seems you're getting this object as a list of dictionary items and the representation is what you see when printed. I believe you can do something like this values = customFieldOptions for value in values: print(value.get("value")) # get the name print(value.get("id") # get the id

May I ask what hosting are you using? Cloud or server? You will need to call the endpoint for get all request types then search for the request type you want in the list and determine what further steps you want to take.

I think the way around this would be to build/create an issue within a project. That would literally translate to an import if you're thinking in that angle. There's no API to perform import per se. However, if you think about, importing basically does a creation of the issue. So if you can literally create the issue in a…