Jack Brickey Expert

You can create a Classic (configurable) board if you like. But you need to set the Location to your profile and then add a shortcut on your sidebar using "Add item". 

Yep. I could recreate. Seems to be a bug. Specifically, I don't believe you should be able to select a parent of type Epic when converting an issue to sub-task. Contact Atlassian Support.

Classic SW. NG has it's own roadmap solution.

you can't build on someone else's app. What app are you looking at or what features are you interested in? You might reach out to the vendor as they may be implementing for Cloud (if the APIs allow). Or maybe there is another app that could meet your needs.

you should reach out to Atlassian Support. I'm not seeing this in my instance.

no. there is already Roadmaps in NG but it is different and separate.

you will need to reach out to Atlassian Support to see if they can assist. 

you might review this article. there may be newer articles and i would recommend searching for posts from others that have done this in the Community for any gotchas. I have not done this myself but the one thing I would convey is to plan your "epic" moves carefully as they don't migrate clean. In other words do the…

you need to go to Project settings > customer notifications and have disable the Create notification (and others if desired).

what is the attachment type? does it happen with all filetypes, e.g. pdf? Do all users see this? Do other browsers result in same error?

this does not sound correct. certainly has not been the case historically but maybe something changed in Premium. Could you share images that convey this.

What about creating a task for every release that has three approval sub-tasks assigned to each dept head? Use automation (addon for server) if you want to notify you when all sub-tasks are complete or something similar. You might even not assign the tasks to the dept heads until you are ready to release. Of course some of…

:-( I had not ever attempted to use PL so was unsure. I may play with this bit to see if I have a better idea but in the meantime here are two ideas (not necessarily great but...) * If the project lead isn't going to change then simply set the Responsible party to the user that is the PL. This can be done either by Post…

Likely. I’m unsure if Project Lead can new accessed in Automation. Have you attempted as yet? trigger - issue created condition - whatever your needs are action edit issue and copy project leader into custom field

No worries. Just click and you are good to go. The only impact will be to your wallet but you get some nice features. 

Is the individual in good working order otherwise? Can he be assigned issues? Can he reorder issue in backlog?

If Classic project click on the ellipses in top right and select Board settings > general

My preference is to go with a Dashboard. However the most important point is to talk to the audience and understand what is important to them. Then construct a Dashboard that hopefully meets their needs if not actually delights them 

Yes. On can make an argument that if the issue is unassigned then neither Jack, Jill nor John are assign to the issue. 

You can’t do that on the portal. If you have a company website consider placing an email request solution there which creates a request in another project. Then you can police that and decide if to grant access.

there isn’t a simple JQL for this but here are you options to consider: * If you use the epic name of the epic in the following JQL - “epic link” = epic-name. If you get no results then epic has no children. Yes not useful when hundreds of epics. * create a scrum board covering all projects you are interested. Look at…

Two methods: * if you use different workflows for each issue type (Classic projects) then use a Post Function on the resolve transition to set field value * Use automation to set resolution once issue is resolved- trigger - issue transitioned , condition - status is Done, condition - if/else block and check issue type,…

i'm not sure what makes up the "status section" and which screen exactly you are looking at but my guess is you are looking at the detail issue view and talking about the right hand column where your context fields are listed. The limit of configuration is presented in the layout screen which can be accessed by clicking on…

as I don't work for Atlassian in any capacity I cannot say why this options has not been implemented. I did locate a suggestion in JAC that you might want to watch/vote as it is currently in the "Gathering Interest" status - JSDCLOUD-4131 . Finally, you might want to try out a Marketplace app, e.g. Queues for JSM or Smart…

Unsure what “sprint planner” means. To be able to manage sprints the user needs to be in a role or group that has “Manage Sprints” permissions so please check - project settings > permissions

If you want to attach a form then just attach it and you can use automation. Understand how this will work though. * Doc is attach and customer gets a link to portal where they can download the doc. * customer edits document and then attaches the edited doc. you can also look to the Marketplace for options. good luck!

Sorry I didn’t assume time literally here I just assumed date. In any event the actual time component of the created date/time will not be show in a list, only in the detail issue view. The column in the list is called “Created”. The JQL field is “createddate” or “created”. 

Certainly the first thing to check. There was a bug about 2y back where this was indeed happening on occasion but that was long since corrected. 

What I mean is that the purpose of having a request type is to actually build a form that collects the required or desired information from the reporter. So I don’t understand why some teams need to acquire more info as a general rule. Why do you need to “send a form” to the reporter? If that is needed occasionally then…

Why can you not create a JQL filter from the queue and then use the results to export to XML or CSV?