Prince Nyeche - ELFAPP Atlassian Partner

What happen to using the name of the issue type? I suppose on server you do get the name of the issue type in the payload? However, I think you can literally build you own unique way using the REST API and get whatever standard you're looking for.

You will need to logout from your browser and login back during the oAuth flow. It seems as though during authentication, it detected that the user isn't properly validated. The callback URL doesn't really matter as long as its a viable URL, it should work.

Hi, if you want to combine this time_in_status function with the pyjira module. You will need to instantiate the LOGIN alias of jira as well before calling that function. Also, you will need to import "PROJECT" alias and "file_reader" function into your script file. from jiraone import LOGIN, PROJECT, file_reader from jira…

Hey @IT Team Your file structure isn't the problem and just to reiterate, the header name to the file doesn't really matter. You just need to ensure that the file has 2 columns and the columns must follows that format of "id" in the first column and "name" in the second column of the CSV file. i.e the CSV file must just…

Yes, there's no export limit. You can go to the doc https://jiraone.readthedocs.io

Hey @vampyren I believe you have the new admin hub and in terms of deleting Jira users yes the user id and user name column that you get from your exported file is the same as accountId and name field respectively. The example I showed as image is a sample to let users understand, that it is an "accountId" that needs to be…

You can always use the get issue endpoint to retrieve an issue detail. Knowing the time_in_status is simply doing a difference between the time that an issue is in a particular status versus when it is not in that particular status. That's how you can determine how long it stayed in a status. I'm not sure I understand…

No, this is a python script. You will need to install python on your device and run it from your terminal or if you have an IDE, you could run it from there too. 

You cannot remove yourself from the site-admin group. You have to use another user who has site-admin privilege to remove it.

Hey @Robert Horan Just to iterate on the tech stuff, this app is completely open source. You can use the source code from Github and run your own build of the app - you do not necessarily need to use the one from Atlassian marketplace (i.e if you can configure it yourself following the instructions). I made it very easy to…

There's no single API but you can combine those API to achieve your aim. In essence, you can create your own APIs out of it and do whatever you prefer within your program.

I don't think Jira server uses accountId. AccountId is only specific for cloud instances.

You've expanded it but you're adding an invalid value transitions.fields which is not part of the available options in search issue endpoint for expand parameter for your API 1. So that should explain why something is going wrong there.

Hi, according to this document you can query the organization API and the payload shows the last_active key. Also, you can vote for this ticket as there's a feature request on it.

Hi, why are you using {{assignee.accountId.asJsonObject("id")}} the end data type is a string so it should be {{issue.assignee.accountId}} for user fields.

Hey @Silvano Your CSV file structure should look like the below image. I suggest you create it using a text editor such as Atom.io To delete users, it must have two columns. The first column and each row underneath it should be for the accountId of the user, and the second column and each row underneath it should be the…

automation for Jira shows you the object how it appears to it as that's how you can access the properties of JSON with automation for Jira. If you're trying to use this object outside of automation to post elsewhere. You should create your own JSON representation by using the dot notation. [ { "accountId":…

You will need to make sure that you've verified your domain in your organization first. Then look into this document specifically to step 3 on DKIM.

You will need to create some sort of datastore that relates an accountId to an emailAddress and call that from a function. On cloud, emailAddress is an object that is restricted based on the users' preference, so you do not want to rely on that object. In terms of multi-picker fields, if you want to append users * Your…

On cloud you should always use accountId when it comes to a user field. In this case for a multipicker field that should be: '{"fields": {"customfield_12904": [{"accountId": "5abcXXX"}]} }'

Follow the same example shown in the doc and ensure that you've generated the correct API key.

Can you add more context to your question? It's a bit ambiguous especially in the context of cloud products!

You should look at your network tab of your Devtool, it should tell you what's going wrong from the response. Most probably a required field or probably, the custom trigger wasn't configured properly.

You should look at this article I wrote a while back. There's a function I made called time_in_status() it can help extract the time in status on any issue on Jira. You can also use a JQL search to retrieve the time in status on every issue within your project or projects.

Hi, Yes it has. In terms of the URL, it is still a direct link to download the attachment. The only thing that was excluded is the filename which comes at the end. This doesn't change the overall function from before.

Are you asking what type of python module can be used to retrieve content from Zephyr API? If that's the question, then you should focus on the requests API.

You can scan the last comment body for a subtext like that using the match smart value and if found close the ticket.

Hey @Pramodh M I never tested it on server but I believe with minor modification to the endpoints, you can get it to work on server.

Just thinking about this, I came up with this script as an example which is completely expandable based on what fields you want.

You have to build your output data structure first if you're going to connect Jira to an external data source. If you want a flat CSV file, you will need to know the exact fields you want to be placed on that file. An easy way to do this in python would be * Define your output data structure. i.e. name of fields you want…