Jack Brickey Expert

Yep I do the same @Trudy P Claspill . Good call out.

Well I would have to say that from my buyers perspective, i.e. the customer, the floating license typically allows a company to serve more of their employees at a lower price point. For example let's say I have 100 employees but realistically I only have 50 employees logged in at any given time. In that scenario, assuming…

Is the “Epic Status” set to Done in addition to the issue status?

What you are referring to is a floating license. Such a license allows you to have say 50 concurrent users logged in at any one time. The Atlassian products do not work on a floating license basis. Rather it works on a named user license where each user must have an Always-On license. 

¿Estás diciendo que quieres que las columnas del tablero tengan etiquetas diferentes? ¿O quieres que los estados subyacentes del flujo de trabajo sean diferentes?

nice idea @Radek Dostál !

Hi Sean, Unfortunately filtered lists Will not show the epic-color. As you noted that field is simply text representation that is used to display the color in boards.

Hi Jennifer, Your options unfortunately are limited. What I have done is to create a project category call archived which allows me to easily see which projects are Active in the project list. I create a archived projects scheme which basically hides the projects from everyone except the admin. However as you have noted…

Hi Melanie, I have never experienced this behavior that I recall. However my instance is cloud from the ground up not a migration. If this is repeatable on multiple spaces in pages than you might wish to have Atlassian support login and have a look. I wonder if the size of your Space is impacting performance?

There was a similar question on this earlier today. I will provide the same answer here. My suggestion would be to export all issues to a CSV file then use that file to import into your new cloud instance. Obviously you will have to take care on what you export and what you import. I expect some massaging of the CSV file…

There isn't any means of altering this in JSM. 

Todas as filas são visíveis por todos os agentes em um projeto. A única maneira de mudar isso é usar esquemas de Segurança de Problemas em diferentes tipos de problemas.

You can have two statuses 'done' and 'done done'. However, for scrum boards only the right most column will be processed as done. All other issues including those in 'done' will go back to backlog on completion of sprint.

Using Automation you can achieve this. Here is an example...

Well if you create an 'escalation' screen and associate to the specific transition to Escalated status it would achieve that.

You can certainly transition the issue to he Pending status and you can have an SLA start on entering this status. However the time component of the SLA needs to be statically defined in the SLA. You cannot incorporate a dynamic SLA time on the fly. I recommend you use Priority or maybe a custom field to direct the SLA to…

Disclaimer- I am just beginning to play with Forms. I suspect this is not possible and my quick search of documentation would seem to gualify that suspicion. With request types for a given portal you can't restrict which customer sees which request type. Since forms are associated with requests there is no way to restrict…

I wonder if you could add a Message custom field above the comment to provide guidance?

Você define Filas para os diferentes agentes. A forma como você define as Filas depende da sua configuração. Em casos de mot, isso será feito pelo tipo de Solicitação, mas às vezes pode ser Issuetype ou Compoment. Seus tipos de solicitação são definidos de modo que os problemas associados possam ser mapeados para uma Fila…

I recommend that you export all issues to CSV and the import to the other instance. Check out this article- create-issues-using-the-csv-importer I would start with a small sample until you get it right then save the configuration file to import the balance. 

Not really. While you could certainly fashion tests using tasks and sub-tasks it isn't a TC management solution.

Nice article @Josh Costella . Indeed getting to the actual requirement is key to delivering the best solution.

ah good point i see this is in Jira collection. @Ira if this is JSW and not JSM then SLAs dont exist OOTB.

Are you on Free tier? If so all users are administrators. 

You could create an automation rule that checked updated date vs resolution date. You could add a label or create a custom field to record the issue updated post resolution. 

No no. There are a great deal of differences here. Advanced roadmaps is part of the previously known as Portfolio product which was built in alignment with Classic Jira. TMP was a ground up redesign so it simply doesn’t fit into the portfolio implementation. At least not yet. 

Yes. You select which issuetypes you wish to associate the new workflow to. If you want to replace the existing workflow entirely the be sure to select all issuetypes currently associated with the current active workflow.

The admin should set up automation for this. Something like... trigger - issue breached SLA condition - as necessary to only proceed with rule if appropriate action - email Assignee

You associate an inactive workflow under project settings > workflows and select Add workflow > add existing.