Jack Brickey Expert

Assuming you are on Cloud here. * backup: Jira settings > Backup manager * end subscription: you have two options here: A) see this article - cancellations-and-refunds B) to keep it active with minimal cost, deactivate all of you users (agents) such that you monthly subscription is a single admin. You can verify billing…

If the user is a member of a group like Jira-users and that group has permissions to each project then they will have access to each. Check what if any group they are members of and remove them. Create a restricted group, place them in that group and set permissions for that group to only the project(s) desired.

Yes. * you need to be admin * go to the workflow that is associated with the issuetype you wish to modify and go into edit view * double click the transition that you are interested in * determine the screen that is used during transition * exit out of the workflow without making changes * go to screens and find the one…

change your workflow to not allow reopening on old issues on comment. consider closing and opening a new one on the customer behalf w/ an explanation.

here is what i see

it is included in the base product. 

if you simply want a ticket created then the user (from email) needs to be a defined Customer. If you don't want to predefine the customers then you need to enable anyone can create an issue under Customer permissions.

Hi JD, i'm just a user like you and while I like a challenge I have a lot on my plate. While it should be all that difficult it will take some time to get everything the way you want I suspect. Something to consider is to reach out to one of the Atlassian partners. Of course that comes at a consulting fee but generally you…

My understand is that when you transfer your data to the new server the existing license will move w/ it to the new serverID. as long as you are only using the same license key on one server you would be fine. If you want more details I would recommend you use the Search box at the top of the page. There are other threads…

you could use Groups to designate the members of the offices.

just stand up the new server and copy the license from the old server and paste to the new one.

* Is this happening to all customers? * How is the customer logging the issue (email, portal, application) * you tagged this as Jira Software as well as JSD. Why is that? Just want to rule out interactions between the two apps. * What specific tests have you run so far?

if you are moving an existing user to an org they will not get an email (i think) but if you are creating a new user then they should get the welcome email.

Please verify that the user is listed as a customer in the JSD project(s). I have many JSW/Confluence users that are also Customers for our JSD projects. The can access all JSW project from the app but only JSD from the portal, unless of course I make them a collaborator in a JSD project in which case they can…

@Tanel Koll, can you please share the details of the bug? was this a fix made by Atlassian? It would be good to include here as it might help others in the future.

When an issue is shared with an Organization it simply announces to the members of the org that they have the option to elect to become a participant. They must act on the initial email notification and choose to participate.

You could possibly use automation, e.g. Automation for Jira, to send an email to the vendors JSD to create the mirror issue.

Pleas consider accepting the answer so it helps future searchers.

You could use automation to create linked issues based upon request type and maybe components. So yes, I think you would be pretty successful with this. The level of success will depend on requirements and expectations.

so your userid is set as the 'run as' user for the automation?

if you do not want to have the ability to have customer share w/in their organization then you simply need to remove the organization. that is all customers should not be in an organization. Having them in an org allows them to share at request with others in their org.

I do not understand what you are asking. Are you asking if you could set up JSD such that some customers (internal or external) could open requests. Then internal resources could triage these request and create linked issues into other JSW or JSD projects?

@Dan Vink, can you clarify what you are wanting to make private and explain why it is not private today?

By default the Time Tracking section won't display for an issue if there is no original estimate. Go to the detailed issue view of a given issue, click the edit look for Original Estimate and if found add in an estimate, save it and see if Time Tracking now displays. If OE is not in the Edit view you need to add the field…

maybe this article will help - how-to-customize-customer-portal-url-in-jira-service-desk-server

what "page" are you looking at? It could be that the comments aren't on that view OR that you don't have permissions to comment. Screenshot?

I'm on cloud and have a similar auto-close automation defined and it works great. here it is in case it helps. One possibility is that your automation is being executed by a user that does not have permission to transition this issue to closed. I would definitely check that. SLA...

i learn something new every day. that is what make the Community fun. ;-)

@Benjamin Slade, if you edit a gadget (each "box" is it's own gadget) then you should see an area to select the filter. If you start typing it will auto-complete so you can select. If you want to edit the actual filter then go to the filter itself, change it and save it. here is an image that might help. If not please…

thanks for letting us know Lee. I would recommend you provide a bit more detail in this specific thread and then "Accept" your own answer so that others might benefit in the future.