Jack Brickey Expert

Oh....unless you are using Team Managed Project in which case statuses are unique to each project. However, I do not believe reordering is possible unless you start from scratch and add in a specific order. Here is an open suggestion- JRACLOUD-81149 

Hi @Jas Aujla , welcome to the community. Statuses are not displayed chronologically, so adding a number in front of your status will not achieve your goal, nor would I recommend that. Check the order of your statuses under settings > issues > statuses. Please understand that in Cloud statuses (at this time) are global so…

I am not aware of a script for this. It appears you have Scriptrunner so I would check the documentation for that. Also check the APIs as it is very likely that is an option.

If you want to find the groups for a single (or few) user then go to settings > user management, find user and show details. if you want to inspect at large export to excel and include group membership in the export.

Hi @Andrew Steele , JSM has two different configurations for notifications: customers and agents/users. Both of these are found under project settings. When you say you only want the reporter to receive notifications do you mean you don't want the agent to be updated? Regardless set up the configurations in the two areas…

Why not create a single rule and add a label each time (strike1, strike2, strike3) and the last one closes the issue assuming that is the final action. Just use if/else block to check labels... if labels is empty or labels != strike1 Then add label strike1 else if labels != strike2 Then add strike2 else if labels !=…

Please check the documentation as it does a good job of explaining the approval configuration. set-up-approvals

Hi @Namrata S Dyaganatti , I checked the status page and all is showing operational. Can you check another browser, though I don't believe this to be a Browser issue. If reproducible please report to Atlassian support.

Hi @Willian Santos ,Se você deseja adicionar um usuário como aprovador a uma lista de aprovadores existente, vá para definir > problemas > campos personalizados e localize seu campo de aprovador. Clique nas elipses à direita e selecione Contextos. Na próxima tela, você pode adicionar aprovadores clicando no valor padrão.…

Hi @Jonathan Veras , did you contact support? That would be my suggestion if not. 

Also, the product team would likely operate within a kanban model, whereas the development team might tend toward a scrum model..

Personally I would create two different boards: product management and development. When an issue created within the product management team is approved then they would create an issue in the development environment and link the two issues. You could either mark the product issue as complete or leave it in some Awaiting…

@Alice Edwards , One thing to add regarding using the components field so that others can be aware before going down that path. Components is a multi-select field so by using this field you could end up with more than one request type in your field which would throw your data off if you were using it for metrics.

Hi @Marta Kopij , what do you mean by the topic is "solved"? if you are referring to this post where someone accepted the answer that simply means that their question was answered. It does not mean that they got the answer that they wanted to hear. If you are referring to some other topic, could you please reference it…

I would like to see a video on this as Nic requested. 

Hi @Alice Edwards , agreed, I don't think a text field will work. Try using single select. You might also try using labels.

Well I'm guessing that the way you solved the other issue is resulting in the xxx@yyyy.atlassian.net where xxx is the unknown causing the issue. Maybe? The from address should be Jira@yyy.atlassian.net.

yes. Each instance is independent.

Hola @sistemas , Puede configurar un controlador de correo entrante para su proyecto (configuración del proyecto, sistema, correo entrante). La advertencia aquí es que el reportero no se puede configurar como el reportero real a menos que se agregue como usuario.

Hola @CoESpainUser , Los componentes se presentan en la barra lateral de los proyectos gestionados por la empresa. Parece que estás en un proyecto gestionado por un equipo.

Yep

Hi @Reb Bravo , you can write the cron yourself but it isn't necessary I think as the Automation presents an easier solution. Before I illustrate this, let me restate what I think you ar trying to do here. * you want to remind the customer daily to take action (such as comment back) * you give the customer 3 chances to…

If you have a single sprint insights will reflect singularly. Sprint insights is associated to the sprint.

Hi @Tom Horton , do you really want to copy an Issuetype? It seems to me you want to copy the workflow and edit the approval placement.

Hi @ORM , what do you mean exactly by progress bar? Can you share the link to the documentation you are referring to? Here is one doc discussing what the timeline view shows - what-is-the-roadmap 

Hi @Saboe, Dave , if each team has their own unique board meaning the issues only appear on a single board then each team would have its own sprint, and thus the insights would be unique to each team and board.

Hi @Anuj Kumar , so there isn't a concept of "project progress". Projects in Jira are generally unbounded. You can have Epics that can illustrate progress. Advanced roadmaps is a concept that often shows progress of Epics. You can include this information within compliance.

Regarding the one issue showing done when you indicate none are done please check the details of the one issue. Does it appear on the board? What status is it in? Could it be that the issue is in Done and the Sprint field indicates the current sprint and somehow it has been hidden from the board, e.g. filter changed during…

Hi @Ketevan Sigua , issues in Sprint are considered complete if they appear in the last column on the right hand side of your board. With that said, can you assess your situation and report back? Specifically, in the image you provided you should have one completed and 59 complete. Are the five issues in the right hand…

I too agree with rethinking things a bit here. Linking the two associated subtasks would be important in solving this as Trudy mentions. In so doing you can simplify the rule to simply trigger on the subtask transitioning and then transition the linked subtask.