John Funk Community Champion

Hola Natalia, El estado Completado debe estar en la última columna del tablero de Sprint para que los problemas se consideren Completados. ¿Puedes compartir una captura de pantalla del tablero que muestre los estados en las columnas?

You are certainly free to offer the feature request of the "pre-create-issue" functionality, but that simply doesn't exist at this point. 

So I am curious who was gas-lit and which comment was made about not complaining? Also, which comment said functionality was not removed? It's a new view, so you can adapt or you can complain. I simply choose to adapt in this case. I was simply pointing out that you can still see the Issue Type by hovering because it…

Hello Everyone! My name is John Funk and I live in Nashville, Tennessee USA I enjoy spending time with family outside of work, including playing cards and board games. I also enjoy reading and watching sports on TV. For me, one of the best things about being an Admin is that I can make the changes that help so many people…

Hi Joe, You actually have to be in a group in order to see and use the group. So if you created a new Group A with 2 users in it but not you, you will not see the group. Add yourself to the group and it should show up after a refresh of your settings screen. After that, you can remove yourself from the group if you like. 

Ah, I see what you are asking now. No, Automation for Jira cannot pre-fill the field as the rule is running. It only fires the action as the rule completes. But it should still be populating the field when the rules finishes. Meaning, in your case that the Description field should be populated. The user can NEVER edit…

Ah, you are correct - I misread the field name. :-)

Hi Maria - Welcome to the Atlassian Community! Epics are just another issue type. And as such, are linked to workflows. So the workflow that the issue type is linked to determines the statuses. So, in your case, it looks like the Epic has been linked to a new workflow within the workflow scheme for that project. Go to…

Each Next-gen project is by design setup to be independent of all other projects. That's really what it is all about. If you need to connect issues between projects, you need to make them Classic Software projects. 

Hi Nikora - why don't you just create a single Issue Security Level and add two entries - one where the Reporter = currentUser() and one where the Watcher = currentUser() Then you can apply the same security level to ALL issues. 

Hi @Sheng Sheng Liu - Welcome to the Atlassian Community! How did you create the feature? What issue type is it? How are you trying to "assign" the feature to the story? Are you using the Linked Issues field?

Hi Thomas - Welcome to the Atlassian Community! I don't think you are going to be able to do that. Next-gen projects use a different method than the Epic Link field to actually link a Next-gen Epic to stories/tasks on that same project. You might be able to create some type of linkage using the Linked Issues field,

That's strange because you don't even have anything in that status. Is there some automation perhaps that uses that status? That's the only other thing I can think of. You probably should go ahead and submit a support ticket with Atlassian here: https://support.atlassian.com/contact/#/ Please post back here what the…

Hi Steven - Welcome to the Atlassian Community! The Automation shouldn't care which create button you are using - it should fire both ways. Is there an error message on the second way? Or does it just not fire and there is nothing in the Audit Log? 

Olá Silva - Não tenho conhecimento de nenhuma forma no Jira Cloud para compartilhar um painel publicamente com não usuários do Jira.

Hi Maritsa - Welcome to the Atlassian Community! Automation for Jira cannot prevent an action from taking place - you need to handle that in the workflow. Edit the workflow to add a condition to the transition to Done. But you are probably going to need an add-on like JMWE to be able to prevent that. 

So it looks like there are cards in the Bug status that need to move to another status before you can delete that status. And it doesn't like the move for some reason. Here's what I would try next, run a filter that looks like this: Project = Panacea and Status = Bug Then see if you can either open each card and change…

Hi Daffy, I would suggest you take a look at Swanly: https://marketplace.atlassian.com/apps/1219470/swanly-project-portfolio-roadmaps-ppm?hosting=cloud&tab=overview They also have some really cool changes coming to the app that you can see previewed in this announcement: https://www.youtube.com/watch?v=sCD5XzBMKOA

Hi @farkhnawaz - Welcome to the Atlassian Community! That is very strange behavior. I would go ahead and submit a support ticket to Atlassian here: https://support.atlassian.com/contact/#/ Please post back here with the resolution. 

Okay, I think I am confused now. Can you walk me through each step that you did and where it is breaking down?

Deleting any issue in Jira is controlled by the Permission Scheme for the project. Even if you are a Jira Administrator, you still need the Delete Issue permission in the Permission Scheme for the project. Typically, we encourage users to NOT delete issues, but to add a status to the workflow for something like Discard or…

Try clicking on the 3 dots menu on the top right of the board and select Manage workflow. Then when you get to the workflow, just delete that Status. 

Hi Paolo - Welcome to the Atlassian Community! Unfortunately, this is not possible out of the box with Jira. See this feature request: https://jira.atlassian.com/browse/JRACLOUD-67108 However, you should be able to do with an add-on like ScriptRunner. 

Here is the bug that was posted for Jira Cloud: https://jira.atlassian.com/browse/JRACLOUD-75982 But it might be the same problem for Server. You should definitely put in a support ticket. 

Hi @rayion - I use the Automation for Jira app for Cloud to do that with a Scheduled trigger type of rule. There is a free app for Automation for Jira for Server, but I think you will probably have to have the paid full app to do the scheduled trigger. You could start a trial with that add-on and see if it does what you…

Hi Alexander - Welcome to the Atlassian Community! Can you provide some more details please - what type of Project and Board is it? Can you share a screenshot of the board? We do not have access to your actual board - nor should you post links to your site. :-) And how are you trying to delete the column?

Hi Nani, It is probably because the board is using a filter that does not include the new issues. Go to Board Settings > General and see what the filter is bringing back and if it needs to be modified. 

Awesome! Yes, the diagram view is always better for me to use. ;-)

Hi Andreas - I use the Automation for Jira app for Cloud to do that with a Scheduled trigger type of rule. There is a free app for Automation for Jira for Server, but I think you will probably have to have the paid full app to do the scheduled trigger. You could start a trial with that add-on and see if it does what you…

Hi Nani, It might be that you used the wrong value for the Location field. However, the Location field does not determine which issues show on the board. That is determined by the board filter - which you already had. So, I expect that the board is showing the right cards, it is just not available through the project you…