Jack Brickey Expert

well as you saw that issue was open in 2014. :-( I have seen some suggestion go very quickly but others take a long time and many aren't developed at all. That said there are, as you imagine, thousands of suggestions out there so they have to wade thru them.

Ok so what I have found is that indeed you can have articles listed w/in a given JSD project in Cloud. Here is how it works: * you create categories for your articles and group articles under these categories * you can choose to "feature" one or more article which effectively pins a link to the article so that a customer…

additionally, it would be worth approaching your coach about the Spotify site. I certainly could be wrong but if it is it is modified or involves an addon I suspect.

thank you for the link. I find it interesting to be sure especially as I was involved in answering that thread. However, for sure I would trust the Atlassian Team members response over my own. I am currently looking into this on my cloud instance to understand how it works. As a learn more I will report back. One question,…

JSD projects fully support independent defined Customers and Agents. They can be completely separate or have overlaps. Hopefully I am understanding your question here. Have you run into an issue attempting this?

this is not possible. The Spotify site is not powered by Jira Service Desk. Can you share the link to the cloud workaround thread are you referring to?

There is no solution that I have seen for this.

Based on what you have stated here it seems that you may not have this new user setup as an agent. Is that possible? It sounds like you are adding a new queue and creating the filter ok but when you go to select the Assignee you don’t see them in the list which would indicate to me that they have not been added as an…

OOTB you are limited to those in the drop down. You might check the Marketplace for potential addons. I have seen on for server but unsure about cloud.

what Are fixed and done here? Statuses or resolutions? You seem to be on the right track. For every transition where an issue is being moved to a status that is of a “done” category you should have a screen with the fix version and release notes. Use validation to ensure the issue has a value or is updated depending on…

I don't use JSU but expect that some required field at creation in the destination project (where linked issue is being created) is not being fulfilled. I suggest checking this by simply manually creating an issue in the project and understand the required fields and see if it yields a clue. Just a theory at this point.

Hi Olga and welcome to the Community. Can you expound on “team calendar “ is that associated with and addon e.g. tempo?

There are a couple of reasons for this. I expect you are looking at a default board on maybe a business project or similar. These default boards do not have board settings. Create a new Kanban board for your project to get full featured capabilities. If this is not a SW project be sure to select your profile as the…

You can use any role or group to be a collaborator. Try creating a group called JSD Collaborator, add your name and add the group to the browse and comment permissions.

@Kasturee , I am on cloud so some things vary from server. As Susan indicated, for JSD you want to add all individuals that can report issues as Customers and you only want to give users that work the issues access to the application as Agents. One caveat is that you elect to define some or all of your JSW users to be…

You might give this a read. migrating-from-jira-cloud-to-server-applications

Yes. You will need an addon for this e.g. scriptrunner 

With JSD you have three options for you customers to create issues: portal, email, and widget. In addition to being able to create issues the portal allows the customer to view, monitor and manage their issues. The other two allow them to create issues only. I if you don’t want to use the portal for you customers you have…

NG projects do not, currently have any concept of workflows at least as they exist today. If you want a workflow then you need to migrate to Classic. I would create the classic project then move all of the data. be prepared for some manual cleanup. Here is a doc to assist.

While I wish that there was something in the Projects view page by default there is not. What I recommend as a workaround is to add a category called Next-Gen and add it to each NG project. This will allow you to (in the future) view all NG easily.

None that I know of. You might check addons but I don’t know if any. Basically what you want is full permissions on customers similar to agent permissions. 

Does this happen for all users? Can you monitor with two user at the same time? My two guesses would be either a browser comparability issue or an addon conflict. To rule out the first try another monitor. To rule out the second assess the addons you have and may disable them one by one. If neither of these are the issue I…

I make use of a custom text field “latest status” that gets over written on a regular basis so that I can show the died o. Dashboards for our weekly status meetings for on project. This overcomes (?) the issue of important info buried in comments. 

This is not possible. You would need two reporters to keep communication separate. Consider creating a clone or linked issue and change the reporter. 

I’m a bit confused. Customers don’t have access to the application and consequently cannot access any Jira dashboards. Ar these “customers” actually portal only access or do they have application access? If the later then you are setting them up with browse access I assume which means they can see all comments. 

Hi Monica and welcome to the community! This is an often employed approach and is pretty easy to do. Just create a new Kanban board with a filter that represents the issues you wish to see. If you need some help with forming the JQL for this please provide some details. You should be able to go to “search issues” and…

That image is from one of my JSD projects. The colors represent priority. AFAIK you cannot change their meaning. 

So this would most certainly be an odd error for trying to create issues. The error is mentioning delete issues are you creating or deleting issues? Regardless check within the project >project settings > permissions and see if the user has creat/delete issues permissions. BTW, deleting issues is not generally a good idea…

You will, or should, install JSD on top of your JSW instance. If on Server check out these instructions - installing-additional-applications-and-version-updates

On Jira Cloud, it's not possible to remove signatures from emails. There is an old feature request for this - JSDCLOUD-5878