Hernan Halabi Community Champion

No, without apps you would have to edit the field and add the options manually each week

Hello @Ousamma Al Rifai if you are talking about internal notifications I would say no. But if it's customers notifications you could disable the default ones and recreate the with automation rules for each request type. 

Hello @Vidhya Mohan I would consider one of these apps to achieve this. https://marketplace.atlassian.com/apps/23337/elements-connect-external-data-fields?hosting=server&tab=overview https://marketplace.atlassian.com/apps/1212096/customfield-editor-for-jira?hosting=server&tab=overview First one would allow you to pull the…

Hello @a.dmitrenko parallel sprints aren't supported yet at next gen projects. Below is the link to the requirement https://jira.atlassian.com/browse/JSWCLOUD-17195

Hello @lukasz.lichota welcome to the community. Have you checked this option? https://marketplace.atlassian.com/apps/43318/power-scripts-jira-workflow-automation?hosting=cloud&tab=pricing

Hi @Robert Meador you can search for me at LinkedIn or leave a message at our website and I will reply through there.

Hola Ornella, necesitaria ver la configuración para validar que no se te esté pasando algo por alto. Dime para que issue type te está ocurriendo también por favor

Hi @Robert Meador a couple of comments. You can't edit the system workflow which is why is asking for a copy. You can edit that one and later you will have to apply it to your projects. Even though the change is simple, if you aren't certain of what you are doing I would suggest you don't do it since you could be impacting…

hello @Robert Meador sorry for the delay on the response. It could be that we are checking the wrong workflow then else you wouldn't be able to move the issues. Please check if this is happening to all issue types or just a few of them. This could help us narrow the scope. If it's only a few issue types, share the workflow…

No worries, looks like you are checking the wrong transition. Notice that the backlog status isn't mapped to a column in the board. That means that tickets with that status won't show on it. On the other hand, you have 3 status mapped to the backlog section of the board and those are the ones you have to check. From the…

What if you check for automation rules? Do you have any? Could you please add some screenshots of the board configuration (the status to columns mapping), the workflow and the configuration of the particular transition related to this? Hopefully this will help the troubleshooting. If the assignment happens before the…

Hello @Robert Meador from the behavior you mention. It seems that there is a post function in the workflow that assigns the ticket to the user that does such transition. You Jira admin can change that within the workflow setting. As @Florian states, there are other ways to achieve the same as well, maybe if you check the…

hello @María Morillo- Velarde welcome to the community. Take a look to the following documentation https://support.atlassian.com/jira-software-cloud/docs/configure-a-classic-board/ You need to check the columns configuration as well as the swimlines. Configure both boards and replicate the setup from one to the other 

Hello @GZ next gen projects can't be configured to be shown in multiple boards as classic projects. That should be the reason why it doesn't show up

I don't know if they'll support this soon. Might be already tracked in their end (can't check now to see if it's the case) Regarding the other item, if I understood correctly you are looking for something like this https://marketplace.atlassian.com/apps/5008/multi-level-cascading-select?hosting=datacenter&tab=overview But…

Hello @KGAFFNEY welcome to the community. If you have that information tracked in your ticket then you can create a report for it. There is no built in solution for this. You could track the cost of each task in a separate field and then just query for issues resolved during the week and should get you a table of issues…

Hello @Petr AST cascading select would be useful if you have them categorized by something that might help to reduce the list of options displayed and you will pick only one per ticket, else you might consider a multi select or single select field. Regarding adding the options, I believe you have to manually do it. Last…

Hello @Jeroen Krause welcome to the community. You could do that with an automation rule. I would run the rule on a daily basis to check if the due date is less than X days (assuming that's the field you are using to identify the deadline of your ticket). Depending on how many days are left, then I would set an action to…

Hello @Tom Bowden sorry for the late reply. If you were able to see them in the past and now you don't, something could have changed on the confluence permissions lesbians the unlicensed users out of the knowledge base. Check this documentation in case it helps…

Hello @Zita Bagi that role isn't created by default in server version. You must check that whoever the user configured in the automation rule has the right permissions over the project. In this case it would be another role within the instance

No es una funcionalidad nativa. Habría que ver si hay alguna app que permita hacer algo así.

Hello @carl.uys welcome to the community. You can see confluence pricing on the following page https://www.atlassian.com/software/confluence/pricing

Hello @Mallikarjuna Madineni there should be no problem to use both instances at the same time even from the same browser. Since they are different they have different credentials and there is no Link between them. 

In most of the cases, the less the better. 

Hello @James Malgieri status names are shared across the whole environment allowing you to reuse it in multiple workflows. If you want to rename it in only one workflow then you will have to replace that status for another with the name you want, not rename the existing one

Hello @thadubsdavid confluence is all about documentation that you could later reference on different Jira tickets if you would like

Hello @kevinstembridge simplified workflow don't escalate at all. You end having tons of workflows and tons of different status for the same stuff like done closed ready completed finished and any other synonyms you can think of. It will impact usability and reporting sooner than performance but in the end it could impact…

Only if you are not on cloud you can do those changes

Hello @Simon Marchant only agents can modify the reporter but you could add an extra field like reported on behalf of and could be a user picker then show that one instead. It should help you achieve what you need.

No, you won't be able to hide that module from agents