Prince Nyeche - ELFAPP Atlassian Partner

Great glad to hear that. Nice workaround.

Hi @Matt Matthias As good as that would sound, no it's not possible. Licensing is the only way around user management on Atlassian Products. If you want to invite users into your Instance without cost, you can do so by removing the Application access from those user. However this will not allow the users to collaborate…

Thinking about this, my thought goes to using the match() but i'm not certain you can strip the entire string (left and right side) out leaving only the accountId.

Hi @Shivam Barthwal For Add-on development, to get expert help on how to develop Jira Add-ons, you can ask here where there are lots of insight. Regarding backend and frontend code, using REST API is the most straightforward way to communicate with Jira, there are other methods as well you could explore such as Forge. You…

Unfortunately, I don't think that you can retrieve such information with Automation. However if your custom field is a multi-line text field with wiki style renderer enabled on the Field configuration, it will render the user on the custom field as you've highlighted, that's the only way possible.

Hi @Mikael Kalla Usernames are deprecated on Cloud, so don't even bother searching for it. Instead you can use Display Name, if you're trying to show some form of string to identify a user. Try the below example and let me know if that's what you're looking for? {{#issue.comments.last}} Comment by: {{author.displayName}}…

Hi @Juan Pedro Silva Using the startAt parameter should get you more results from the changelog endpoint just as @Daniel Eads mentioned. Therefore the behaviour is expected as the default is 100 unless you specify to loop through the records.

Hi @Venkata Ramana Redddy You can use the Issue Search API to get bulk issues, that should give you the field for Issue type.

Hi @Carolyn Barbierato Parent Link field is created automatically, please follow the below * Go to your Project Settings > Screens * Under the Epic issue type, click to add a field to the screen. Depending on if you've separated your Issue type screen scheme * Search for the Parent Link field and add it * Navigate to the…

Hi @Poorvi Dharwad You will need to use API to update the issue link type if you're targeting a bulk edit.

Hi @Neeraj Kumar I don't think that's possible as that it built into Jira's Issue web panel since Automation is now native to Cloud.

Hi @Omkar Pendse You will need to use API if you're on Cloud to do such. If you're able to get a workable script that can run in a loop across the number of issues you specify. You can specify that by reading the issue key from a file, most preferably a CSV file.

I think, that has been a long standing issue with how Jira works because all users when not using an Application should be deactivated but your use case shows otherwise because you have multiple Applications, so deactivation should be done per Application that way it can work as expected. However this won't happen because…

Hi @Vikram Singh You can look into Jira Webhook for outbound from Jira, however those are limited to the events available. 

Hi @Arthur Osman If I'm not mistaken Microsoft is suppose to discontinue it soon, but I believe they've extended the timeline. On the other hand Google is still supporting it for the meantime and should follow suite. Atlassian has an EAP release for oAuth but I believe by the time providers such as Microsoft and Google…

I guess it wouldn't since that the situation.

Hi @Veeranjaneyulu Kureti So I examined the json and it seems that the way you nested it was wrong. all those other fields should be nested inside of the "field": { } element. That's why that error was occuring. I cleaned the code up a bit for you. Please give it a try. import requests import json from requests.auth import…

Hi @Patrick O_Hara You do not need to base64 encode the email and token, see example below and see if that works for you. import json import requests from requests.auth import HTTPBasicAuth email = "youremail@example.com" token = "APITOKEN" auth_request = HTTPBasicAuth(email, token) headers = {…

Do you have a Project with id:10000 on your Instance? you might want to check the Id of the project you're trying to create this issue on.

No you will not, your license will port over once the upgrade is done.

Hey @Veeranjaneyulu Kureti If you simply want to create an issue, use the create issue API to do that, in your request payload that's where you specify the project to connect to. Creating Issues or Projects are separate APIs, so if you want to do either use the designated API to achieve your aim.

Hi @Veeranjaneyulu Kureti I don't think you're connecting to the Project API hence such error. you should use in the url variable. https://rasateam.atlassian.net/rest/api/3/project Then specify the fields you want available during creation in your json payload. A Python example is shown on the developers doc here

Hi @Thuong NguyenVan * Look at the Update requirement, so you're sure of what changes or system requirements are need * Follow the Preparing for Upgrade steps * If you have any add-ons, disable that first before upgrade, then enable after upgrade is done * Prepare a backup copy of your Installation directory and your Jira…

Hi @Brady Phipps What you can do here is change the Email request email prefix and test that if it works. e.g helpdesk@<yourinstance>.atlassian.net. 

Hi @Christian Rieckmann Start by inviting your collaborators. Then you can be able to use Jira with them. Also you might want to look into * Permissions * Managing Permissions * Licensing * Notifications For the platform of Jira you're using.

Hi @John W The application access feature is meant to allow administrators to control which users have access to Jira applications, regardless of whether that user is currently active. This is explained here on what is to be done for your users. Therefore the expected behaviour here is to deactivate the user instead of…

It shouldn't send the notification in the first place as the default is false, even if you pass it as a parameter in the request body it doesn't work. I don't think that API is particularly working well for the notification part. There's a report ACJIRA-1818 by the Atlassian team, something I think you could watch.

Hi @Glory Mercy Please try to check the below: * Ensure that the story point field is added to the screen of the Project * Ensure that on your Scrum Board Settings > Estimation your Estimation statistics is on Story point and time tracking to None. * Check your Custom field Configuration context (Jira Settings > Issues >…

Hi @VACH SITC There are two things you have to take note of: * Jira users created via the API, if the default product access is turned on, the default group will be assigned if the default is "jira-software-users" that will give them application access. * The Portal access depends on your settings on the Jira Service Desk…

Hey @Raghu Boyapally are you referring to idea of changing an email address then unclaiming the domain, what happens to the user? If that's your question, the user will still be able to access their board and activities using the new email address as that get linked to their Atlassian AccountId.