Jack Brickey Expert

I may not be following so let me step back. Basically, in JSD there are Agents and Customers. Agents are those that are assigned and work issues to resolution. Customers are those that create the issues. As an admin you can add agents into a service desk role w/ certain permissions. Customers can be added automatically as…

I don't understand the question. Could you please provide the details of what problem you are trying to solve? Maybe an example would help.

i'm unsure where the issue might lie TBH. I'm thinking you have some script or permission scheme possibly thru third-party addon that is interfering. I'm tied up today after returning from vacation and would recommend you reach out to Atlassian Support or waiting for others to chime in here.

I see u have "Service Desk Team" project role as being able to Assign Issues which is good. Now check to ensure that the users are in this role. If they are then the user should be able to assign an issue to another agent.

you need to go to project > project settings > permissions and ensure that the desired users are included in the Assign Issues permission.

and it didn't work?

@Daniel Niccoli, you simply need to add each client email as a "Customer" for their associated project and enable email creation. This article might assist. You can enable "Anyone can send a request via the portal or 'email address' in project > project settings > customer permissions

if you are trying to set it to the Component Lead then yes you need to set the component during the creation. Now if there is only one person that you will ever assign to and you don't want the customer to select the component then you could elect to simply set the assignee as a Post Function for the Create transition.

how many JSD projects do you have in your instance? I just enabled on my instance and see the below. You should have one 'tile' for each project you have. If you only have one project then unsure what it will look like.

If you click on the Organization under the Customers menu and use "Add Customer" it will simply move them if they exist in 'root' of the project. I wish you could simply have a check box where you could move multiple from root but it doesn't exist. :-(

And if Nic’s answer isn’t hitting home please explain what you mean by “some of our setup options are not available”. Where are you looking and what are you expecting there?

Also check any automation you have.

That sure feels like a bug and as such I would report to Atlassian Support.

No. You can create a new project and move issues over.

Yay for "publishing"! Yay for "related content" relo!

go to project > project settings > portal settings click on view and customize link then enable as shown below

thanks for adding @Manon Soubies-Camy that is a useful article.

@Marie Piquemil, roadmap is only available on the new Jira next-gen projects not the classic projects. Create a new project using the next-gen template.

@Rohitash Pathak, as a user like yourself I’m not available to do a webex with you. Server looks quite different than cloud, as such I will reach out to other Community Champions to see if they can assist. just to be clear have you verified that the other user himself is logging in and seeing both projects?

There has not been any communication on when or whether this will be brought to Server. 

The Organization is a way to group user basically. Users within an organization can share an issue with other user in the same organization. Think about this scenario: * two Organizations: Org1 and Org2 both being supported by a single project in JSD * Org1 has users: Fred, Sally, Ivan, Cindy * Org2 has users: Donna, Bill,…

Also consider the two-dimensional gadget. I find it quite useful.

While the following isn’t exactly what you asked for you might find it useful. create a dashboard and use the two-dimensional gadget with y-axis being reporter and x-axis being say issuetype. Use a filter that is for the last 30d or similar.

For now it is not supported but am sure it will be added in the not too distant future.

There should be a specific automation function for this already - Update when Linked issue changes. At least this is the case in Cloud. if not here is an example to get you started. It is specific to my workflow so you will need to adjust.

I believe you would need an addon like Scriptrunner for this. With this addon you could leverage the addedaftersprintstart to get what you wanted. You could adopt a manual procedure by adding a label to all issues just before starting sprints. as you said you can see this in the sprint report too 

Ah, yes that is likely the case. Basically the user needs to have a paid license of JSD to create a full dashboard. But the best solution is to simply set it up and share as an admin. Note, one think I like to do is to create a “currentuser” dashboard by creating filters using “currentuser()” function in JQL. This allow…

@Rohitash Pathak, welcome to the Community. First let me convey that for the most part the Community is made up of users such as yourself but there are Atlassians that support as well. This simply means that support for questions is a volunteer activity primarily. Also, I see you posted several iterations of the same…

your best bet is to look at available addons. check out these

i have not seen any notification of this being put into Server. IMO, I would be surprised if the next-gen concept and associated Roadmap feature found it way to Server for a long time if ever. Maybe someone from Atlassian has a better answer for you and will chime in here.