Jack Brickey Expert

@sergioruedavalid, you can look at these. JMEH seems to be one of the more commonly used but I don't have experience w/ or promote.

@Michelle Vidler, do you mean how to use the UI to navigate to view all boards? Boards>View all boards of course the navigation depends on cloud/server and version. If the above is what you meant I think your original post conveying "link" thru us off here.

that is a pretty messy filter. :-( so...wouldn't simply creating the boards based upon the "Team Name" work? e.g. AGV Board - "Team Name" = "AGV HW1" If I am reading you correctly, all issues associated w/ a team ultimately will have the "Team Name" field set. If not already the case that field should be made required at…

@sergioruedavalid, AFAIK there is no way to do that at least not natively. There may be a plugin that would work but if you are on cloud that limits your options. With that said, might I ask why you would want this. I'm wondering if rather having a single project using Components w/in the project to differentiate. Of…

@Nick Knuth, If i understand your issue and goal correctly it is certainly solvable thru proper filtering for the board. However, to assist I would need more info from you. Can you provide the details of your current board filter? Ahead of that let me ask a question and make some comments that may help. * Are the boards…

@talianassiforbes, requests are just issues, defects, tasks are "issue types". So the documentation for adding approves applies to whatever issue type you want to apply it to. LMK if I'm misunderstanding your question.

@Gennady, this can be controlled w/in the permissions for the project. By default (for me in cloud anyway) users w/ Jira/Core can create JSD issues. If you don't want them to be able to then go to Project > Project settings > Permissions and change the Create Issues permission. @Tinker Fadoua, no additional license is…

yep bet that is the issue. Go into User Management and click JSD access for Danny.

If you haven't yet tried another browser I would suggest doing so. While it could be a browser issue I would suspect something else first. But, if the other browser (IE, Firefox) then it sure could be. 

@Hema Roshini, adding to Nic’s note here. You indicate you have JIRA admin access but cannot edit project settings which you should be able to do. Can you provide more info here? What are you trying to change? It might help if you show an image of your actions.

do you have the permissions set to share? Projects/Project settings/Customer Permissions (see below) and do you have an Organization defined w/ all members of that org in the Organization?

ok. so aside from the "assign to me" link, can Danny click on the assignee and enter any of the service desk members and/or himself.

@Kathleen Ellis, have you tried editing the permissions to allow Service Desk Team Members to assign issues. Can you provide a screen capture of your current permissions?

@Javier Rivera, have you verified that you have the Description and Summary fields set for this issue type? Project Settings, Issue Types, edit the type.

I like the approach Susan and may look at this as well. 

@Greg Obleshchuk, this is documented in the Atlassian documentation so I encourage you to look there. The reason for this is that the details depends on your version, Cloud or Server and whether you are using the new UI experience. With that said here is how you do it on Cloud w/ new UI. * click on magnifying glass…

My use case is internal but I would argue that it applies to external as well. * You absolutely allow customers to select priority but... * You publish priority definitions as a knowledge base article and ensure customers read when they come onboard. The article needs to convey that priorities may be adjusted to align with…

@Rita Carnes, the answer that @Gregor Kasmann_Actonic provided would work. However, having 25 swimlanes would be, IMO, less than ideal. But this is a personal choice. You could also consider: * 25 boards - clean but a lot of boards to deal with. :-( * 25 quick filters - efficient and results in single clean board allowing…

@Mukesh Bathija, welcome to JSD. As you are likely aware you can customize to your needs/liking so if OOB isn't what you want feel free to customize. 1) It has to do w/ the workflows associated with the issue type. More or less as you indicated. 2) yes both are needed I think. Basically, Waiting for support indicates it is…

@Mizan, yes understood not for JSD but I'm not seeing for Jira (cloud). @Thomas Schlegel, good to know it is still there for you. Now where has my little friend disappeared. :-( Maybe a cloud thing?

Anytime! Glad to help.

@Jamel Boustaoui, is this when creating the issue or when you are editing an existing issue? If you are editing an existing issue of say IT Help then the only issue types that will appear in the drop down will be those associated w/ the current workflow. If you want to change the issue to Service Request w/ approval then…

Then the issue needs to be assigned to the person that is to answer the question. If you leave the 'answerer' out of the Jira workflow then that is a hole in the process. The idea is to always know who has the ball when an issue is underway. In JSD there is a "Waiting on customer" status which is similar to assigning the…

@Ella10004, yep. you can change the issue category of the "On Hold" status to be "To Do" then configure the board to move "On Hold" to the column that contains "To Do". IMO on hold items should always be equivalent to "To Do". If they are on hold they aren't in progress they are 'previously in progress'. If you want to…

@scherbank, that JQL will not produce the sub-tasks. Since sub-tasks are not directly associated with an Epic they will not show here. The only thing that would show from the above are the Stories associated with the "XXXX" epic link.

@Adriana Wolfe, did you ever get this resolved? If you are still experiencing I would suggest opening a support ticket w/ Atlassian.

@Ryan Finco, So I’m not where I can try this but if you hide all issue types other than “New Issue” then I think that should work. The customer will only be able to create New Issue but should be able to continue to see it on the portal once the agent moves to another ‘hidden’ issue type. To do this i would suggest the…

@Jamel Boustaoui, the Customer Notifications go to users defined as customers. The notifications received by users with application access (agents, admins) receive the standard notifications as defined under the “Notifications” settings. 

@Shannon S, yep understood. Just wanted to hear if Abhijit’s questions were answered.

@Abhijit Kirdat, you seem to have reposted your question as an answer? Did you see the info from @Nic Brough -Adaptavist-.