Prince Nyeche - ELFAPP Atlassian Partner

Hi @sushanth_shettigar Welcome to community! Such an API to list the last login doesn't exist or is not public yet. And I don't think this option would be available without some form of Atlassian access feature. Likewise, the minimum requirement needed for a user to use the api basically depends on the permission the user…

Hi @Ashok Yes, you can look at the api documentations here and see which aspect meets your need.

Hi, I already gave a link to the docs in my previous response.

No, you just need to simply make a call to the method field.update_field_data() Example usage: <span>from</span> <span>jiraone</span> <span>import</span> <span>field</span><span>, </span><span>LOGIN</span><span>user</span> <span>=</span> <span>"username"</span><span>password</span> <span>=</span>…

Hi, you can look into using API to do what you want?

Yes its global, you can't have IP whitelisting on a set of repos and it's not available for free plans. Having a demo of premium plan means reaching out to Atlassian and requesting for one if you're really certain you want to make a purchase. Atlassian access on the other hand comes with the trial of 30 days. However for…

Hi, "Application" meaning the Atlassian app used per organization. In your case bitbucket as a whole. However within the concept of cloud, it would basically mean any project(s) / repos you have within your bitbucket organization account and not necessary towards bitbucket application. The link you sent I believe speaks…

Hi @Stephen Ellwood Welcome to community! On Cloud I don't think it allows raw HTML to be added directly. If it was on markdown most probably it can render it but HTML, it will most definitely strip it out. 

Hi @paul_nerie_1902 Welcome to community! IP whitelisting feature for premium plan is done on an IP or IP range basis per application in your organization as it uses CIDR notation. So if you configure an IP, only that IP will be allowed to access the application. 

Hi @Arjun Eswaran Welcome to community! Those type of fields are a bit tricky to work with. However I have a script called jiraone that could help with updating the field options on various issues while maintaining the previous values. It has a field variable you can use to call defined methods used for updating Jira…

Hi @hmnaqvi Removing users on cloud, doesn't mean that the user will be removed completely. Atlassian uses a directory that ensures integrity between users base. So what it does is make the user not visible on the UI, however behind the scene that same user is just inactive. This helps to re-associate a user in case you…

Hi @hmnaqvi Now this is the part that might get confusing when it comes to cloud. So I'm going to expand on it. This is not exactly true because I'm getting qm:code in return from API for an agent on jira service management. That user isn't a customer but an agent on JSM. If you're getting a JSM agent as <qm:code> the only…

Hey @hmnaqvi I think there's a confusion here. The <qm:code> is a different kind of accountId specifically to "customer only users" on Jira Service Management. Now the other type "5ab599xxxxx" - this is accountId for any other Atlassian cloud user. You need to know that these two users are distinctively different and can't…

Hey @hmnaqvi based on your question, you wanted to know why you got the <qm:code>. With that fact, you only have one option. Either you filter it or get everything. So it can't be for some users its working fine and other it's not. It doesn't seem logically that way. You definitely have customer only users on your…

It's getting better every time. The advancements I've seen so far is truly remarkable. The future is very bright with Atlassian cloud suite.

Hi @hmnaqvi Welcome to community! That user will be a customer only user. The reason for that is because you have Jira Service Management application and that too has its own user base. What you should do is filter the accountType from the API. when calling Jira users, specify as: "accountType": "atlassian" To return only…

Hi @Peter Månsson Hansen I don't know if you still need help on this, but I do have a script which builds a report based on certain parameters. How it works is, you can give it your user's display name, in this case your customer user. Then it will search for any issue where the customer is the reporter using jql, get the…

Hi @韦哲 Welcome to community! You will need to find a user first in order to extract an accountId. Better to search all users out and filter the ones you need based on displayname or email_address. You can use the endpoint /rest/api/3/users/search to search for every user on the instance and perform filtering OR I have a…

Hi @Yatish Madhav You could reach out to an Atlassian partner to help you migrate those projects or provide a technical consultation during the migration process.

@Harshit Somani according to the docs for PUT method, it accepts origin being a dict, however I'm not sure if that includes additional fields other than appKey and originId.

@Harshit Somani I'm not particularly sure why probably you can perform some troubleshooting steps to determine why it happens.

Hi @Davoli Sandra It's better to ask your colleagues or peers or ask your IT team (if any) so they can help you out here. you should start first by reaching out to your direct manager to enquire if there's a process involved.

Glad to share the knowledge @Jimmy Seddon 

Hi @Davoli Sandra Welcome to community! The first thing you should do, is reach out to your Administrator to provide you access. If you have an IT Service Desk in your organization, you could reach out to them and raise a request and explain the issue you're having and how they can help out.

Please can you also explain your use case here? What purpose does it serve to a user using it? A Status in itself basically just display the progress of the issue or ticket. I don't particular see a need why it should be required. Most users would rather hide the status but making it required serves no purpose in a…

Hi @tal Welcome to community! Can you elaborate more on your question on what you mean by make one of the statuses required when field is marked "yes"? Is statuses a field as well or you're referring to the workflow status the user will be transitioning to?

can you see the "edit issues" permission under Issue permissions from Project settings > permission ? That's where you should be looking at.

Hi @Edoardo Polito Welcome to community! In a Classic project, editing a field is done in line of the issue view (based on the new issue view). In the event a field cannot be modified then the users do not have Edit issues permission in the Permission scheme. There's no modify contact permission on the permission scheme.…

Hi Monisha There are various ways to go about this but first you have to describe your use case in more detail as that would give us better context on what you want to achieve. If you just want to set a default assignee, you can use * Components * Project lead * Post functions * Jira automations etc Just to mention a few…

Hey @Michel MDM Unfortunately raising support ticket isn't available for free accounts. Likewise are you referring to the general language configuration of your instance? If not, if its for your own personal language preference, you can simply do that from your profile personal settings instead.