Prince Nyeche - ELFAPP Atlassian Partner

@Michael Schmidt If all fails, the best way to go about it, is to test it out on a different permission scheme. Do not copy it, replicate the permission scheme and try the endpoint on the new scheme and see if the behaviour occurs.

If you're asking whether you can add attachment during issue creation, then the answer is yes. You have a description field where you can add contents there. Otherwise, you should add the attachment field to the create issue screen.

Hey @LAXMI ABHINAV REDDY ARAE Can you edit that question and split it into different new questions on its own for each of the question. That way you can get better response on the questions.

You do not need to migrate the API endpoint, that's inbuilt within Jira Datacenter and accessible with the right credentials of an active user. 

Hey @Jammy Li , No, on a free cloud account, you can't do any of those. You can't tweak the permission (for Software or Core) or add people from the project. Except you explicitly invite the users from your admin hub limited to your 10 user count.

Hi @LAXMI ABHINAV REDDY ARAE Please can you elaborate on what you mean by "migrate API Service accounts"? or Are you simply referring to migrating the users?

Hey @Tanya B. there are two approaches here you can consider. Either you block access for the entire project, or you block access to issues within the project. The former is done on permission schemes which will involve changing roles within your user's page. This design has to be straight forward enough, so you can change…

Hi @Shawn Most probably you're making too many request from your instance. An example can be as a result of using boards that fetches a lot of issues to load or sending too many webhook triggers.

@Nic Brough -Adaptavist- Haha...I like to travel light. So the lighter the load the better. Hmm come to think of it, it wouldn't be bad to carry some tea bags. I always thought how cool is it to sip a cup of tea in space 😆

For the most part of it, I think I will go on the bare minimum 😅. * A phone with my music playlist and photos. * A laptop - because I will need to watch all those star-trek movies on a bigger screen. * A pair of socks - space is cold you know. * Wireless headphones - In space no one can hear you scream, so need the music…

Having 2K users in the same group and used across multiple project in roles is bound to cause some problem at a future date. One of the things you could do is revisit the group and structure it in a way that it can be easily managed. For example, removing one user from the group is easy enough, create another group with…

Yes, Jira-admins can adjust it but I think it's through the permission scheme which is a manual work if you're considering multiple projects and also take note that multiple projects can share the same scheme which makes this a difficult feature to implement.

Hey @yewujie All you need to do is to be able to identify the user and get their accountId, this is done by first searching for the user using the search user API. Then add the user to an existing group name or you can create a new group and add the user there.

The alternative is to use an addon as suggested on one of the comment on this ticket JRACLOUD-5052 

It would be easier if you could use an addon such as recurring task for such onboarding exercise but then again you can always use automation to copy values from one issue to another.

Ok, once you get the url for the attachment that's one step, how do you post back a binary data to Jira? What I'm thinking here is that using a webhook service, you can send the request there (which includes, the instance url, issue key, attachment url) and the webhook service will extract the file (authentication is…

Hi @Steve Arch Welcome to community! I think that is done based on the permission scheme and by default app users account has access to all project. Something to think about, in your app you can access the permission scheme API and update the configurations directly to restrict the app - I think that's one of the ways to…

Hi @Jose A. Íñigo If you're certain the key is not used, then the error won't be displayed. Most probably you have installed this app as a private app by uploading on your instance and now you're trying to install it as a cloud app. That's where the duplication might probably exist. 

Hi @Chris Fortmueller Copying attachment from one instance to another or project to another is very possible via API. However using automation and webhook seems more like manual task would be involved rather than it being automated. i.e. how will the attachment url be extracted dynamically using automation and how would…

Hey @Tanya B. In the first place, using groups in project permissions doesn't scale your Jira configuration. You should use project roles in your permission schemes that way, you can know which group can have access or not based on the permissions that has been defined. That way, it goes on a project basis. Using…

Hey @Bob Jeruchim There's a step within the import process that tells you if you want to retain the link or change it. What did you select on that step? If it's the attachments are not working, I suggest you perform the same restore again on your new Jira instance and this time, watch out for any prompts.

Have you thought about using Automation?

Hey @Alex L. Lacanilao Jr. Glad it worked out well for you. All the best.

Hi @Alex L. Lacanilao Jr. Removing a user from group API doesn't remove the user from both application group. You have to specify which group you want to remove and that specific group is removed from the user. If in your case you get a different result, probably you should share the API specifically that you're using.

Is not possible that way if those users are customer only users on JSM. The only way I can see this possibly working is if those customer users have confluence license, then you can restrict the KB pages to "private" using confluence permission which can be tailored to specific groups (i.e. specific company) in terms of…

Hey @jlee Hmm this is a bit tricky. I'm not sure if JSM has such ability. Normally the KB can be visible by labels but on the portal it doesn't matter which organization the user belongs to. So restricting an article based on the organization would be nice but I don't think that's an angle JSM is heading to. May I ask…

Yes, by using a simple text field custom field which the user must update.

Not possible to use a user_picker field to display email address. It should show the name, except the user changes the Atlassian account full name to an email_address

Use automation especially the assign action then choose user.

Hi @Mateja Jermanis While that would be nice to have, it doesn't work that way for the roadmap view in classic or next-gen projects. Atlassian has Advanced roadmaps which is a premium feature that can do what you mentioned as it can pull out multiple boards into plans. If you have the budget for it, I will suggest you try…