Jack Brickey Expert

please update here once you get your answer.

You are on Cloud platform and the app is only for Server.

I use this addon - time-reports 

so you can remove them from the project by going to project settings > people and click "remove". you can remove their access to the entire instance (any/all projects they may belong to) by going to Jira settings/cog > user management > Jira Service Desk in the sidebar, find the user and click the ellipses and "revoke…

While Cloud is priced per user, Server is tiered pricing. You can get a quote if you like here as I see it the tiers are:

WARNING: Editorial.... I don't think this is the correct answer or at least it is incomplete. You should not make the Resolution mandatory in the Field Configuration screen. As Nic so eloquently put it below... NEVER do that. And in a similar vein, NEVER put the resolution field on any screen other than a "transition to a…

just so we are on the same page can you provide a screenshot here of where you are at.

Check that they actually have the necessary permissions under project settings > permissions.

Never make Resolution required in field config.

The free plan does have some limitations but I would think the Widget is one of them TBH. Can you try a different browser just for grins?

Ah I see. The conflict is that the epics are assigned to others. Can you test leaving the epic unassigned? Or maybe try this filter for board... issuetype != epic and assignee = currentuser () Need to play with this a bit if neither work and will do so when I have a moment.

I would recommend you read the intro documentation on JSD to get comfortable with the app. You can find documentation here - https://support.atlassian.com/jira-service-desk-cloud/resources/ with that said.... creating a custom field Once you have a custom field it would need to be added to the Request types on the portal…

You add an existing user into an existing org by clicking on the org under Customers then adding a member which move the user from ‘root’ to the org. It will create a user if they don’t exist. you remove a member from an org by clicking on the “x” when you hover over the user.

So is the issue still being investigated by support?

This will only be available for Agents of the project. 

You might be interested in this thread - The-new-policy-All-members-with-admin-permission-seems-very-bad 

Hi @Korbinian_Donhauser , welcome to the Community. I’m a bit confused. At first blush it appears that the board is doing what you initially stated was you requirement but your last comment “but does not show the issues linked to an epic assigned to someone else.” contradicts your goal, seemingly. if you use assignee =…

I would create a separate project altogether and restrict permissions. Then move the issue to the other project when approved.

It may be that the Widget Feature isn’t supported in free plan. Unsure if that is the case or not. I will see if I can find any data on that.

Hi Phillipp, welcome to the Community. There is, to the best of my knowledge no way to do this. Can you articulate why you would need to do this vs. simply creating the form directly in the request?

And if you want to “require” an update to the Assignee.... Step 4: add a Validator for field modified

You are on Cloud, Archiving is only available for Server/data center.

Sorry I missed the api bit in the title.

So do you really need to make the issue not discoverable altogether or what if it isn’t shown on the board at all? You could create a unique status and simply not map it to any board column. Now a user with appropriate project permission could search and find the issue if they were so inclined but you can restrict who can…

Hi Dennis, welcome to the Community. First, you don’t assign individual issues to teams only to a single user. In JSD you will have Agents that work the issues in a given project. Typically for my SD projects, issue are created as Unassigned and all issue go into a Triage queue which all agents monitor and assume ownership…

If you are an admin you can go into settings > issues> Issuetype and determine the Issuetype schemes which may give the full view but best to then cross reference with the Issuetype schemes which provide project usage of the aforementioned schemes.

If you are using a Classic Kanban board and can configure the setting you can control the sharing of the board but if you want to control what they can see/do that is done at the project permission level. What precisely is your goal. Note if you are talking about the default boards created with some projects they cannot be…

This is not supported OOTB. There is a suggestion you can watch/vote but I am not optimistic that it will be addressed given the comments. JSDCLOUD-1393 . You might consider an addon, e.g. JETI or similar email handler app.

I didn’t even think that was possible. What you need to do is to combine them into one and remove access or delete the other. Run a query for each username and fin the one with no or fewest number of issues and move them to the other username (assignee, reporter, watcher, etc). Then go into settings > user management and…

If the user is in the system, has create and comment permissions then I’m unsure. I would reach out to support.