John Funk Community Champion

It might be best in that case to create separate plans for each structure? 

Yes, in your case, I would use Components. 

Hi Kyla - Welcome to the Atlassian Community! Since they are different clients and you have separate "accounts" for each, I would even consider creating a separate Project in Jira for each client. However, if you have the same team working across all clients, simply creating a Component for each client should work well. I…

Hi Alex - Welcome to the Atlassian Community! Check the Permission Scheme for each project to make sure that you have Browse Project permissions in each scheme. Administrators do not have automatic access to all projects.

Do both of the sub-tasks use the same Workflow? If not, you should look at the transitions for the QC sub-task to make sure that add-ons are not excluded in any conditions. 

Well, that was written before the announcement came down. Hopefully, there will be some solution prior to the forced switchover. But for now, it remains an option. 

Hey Kara - without jumping into this too much, what if you did the following: In the first condition text above, change "not equal" to "equal" and change "NULL" to "Yes" Get rid of the 3rd condition and move the 4th condition up to the same level with conditions 1 and 2 In the 5th condition - do the same as you did in the…

Hey @Simmo - This is the second time in a couple of weeks where people are having trouble in Automation with the Target Date. It "seems" to be a typical date field type, but it doesn't behave as one when using Automation. Thoughts?

Hi Kelly, Yes, you can do that with Automation for Jira. You will need some type of trigger event, but when that happens you can automatically create multiple issues, including Epics. 

You should be able to go to Project Settings > Access and remove the user from access to the project. 

Oi Ana, Você precisa desconectá-los de quaisquer Esquemas de fluxo de trabalho ativos. Se você deseja se livrar de todo o Esquema de fluxo de trabalho, você precisa desconectar o esquema de todos os projetos.

Great! I should of thought of that in the first place haha

Also, just verified from another Community Leader with a Free instance that it worked for him. You will need to start typing names of people for them to show up - they don't just appear in the list. 

Sorry that didn't work. I would just go back to the All active users are allowed function then for now. I am trying to get someone with Atlassian to provide an answer on that custom field type. How many active users do you have in your instance? 

Hey Ian, I have to be honest, this sounds pretty convoluted to me. I think you would be better off sticking to a purer form of Kanban or Scrum. But that's just me. The only suggestion I would have is to clone the issue when it reaches Done on the Sprint board and then work with the Cloned card on the Downstream Kanban…

Hi Arjun - Welcome to the Atlassian Community! Is this a Next-gen Project? Or a Classic Software Project? 

Hi Lara, I have not tried to add two levels yet, but I am suspicious that it is enforcing a rigid structure where each level must be in place. In other words, to have a Portfolio Epic, it must have a Feature, too, for the Epic to be attached. Just guessing though. 

Hi Robert - You can create a filter for the issues you want to see. Then you can export from the filter. 

In your list you should use jira-software-users

De nada :-)

In my testing, no you cannot link multiple project issues to a Next-gen Epic. Only issues on that Next-gen project can be linked to that Epic. 

You create a board and then attach a filter that spans the projects used by the boards. 

Hi Kyle - Welcome to the Atlassian Community! Yes, an Epic can be linked it issues across multiple projects for Classic Software Projects. 

Sure for Classic Software Projects. Just create a workflow that has all of those statuses and then you can attached the Workflow Scheme to as many projects as you like. If you use Next-gen projects, you would have to create the columns again for every Next-gen project. 

Hi Cheryl, I have not used the free plan so I am not sure of what the limitations might be. However, maybe you could try linking the custom field to a group in Jira. Go to Settings > Issues > Custom Fields and search for your field. Then click on the 3 dots menu to the right and select Context and default values. At the…

Hi Nagaraj - Welcome to the Atlassian Community! You are not able to do groupings of columns like that on boards in Jira. You can have the individual columns like you have - but you would need to label more like: REQ - To Do, REQ - Doing, REQ- Done, Design - To Do, etc. Then you would need a status in your workflow for…

Hi Reddy - You would need to create a custom number field and populate it with the ranking of each one. Then you can sort by the custom field. 

Hi Fiona - Welcome to the Atlassian Community! Depending on the number of issues you have across all projects, that might not be a good idea as it could bog down the board and not load properly. You could use Dashboards to help see the progress or an Advanced Roadmap as Prince suggests - but you would need to have a…

Hey Gil, Here is what I would do - I would create Components on Project X for each platform - Platform 1, Platform 2 and Platform 3. Place one component on each issue in the project. Then I would create a single board with one Sprint. Then create 3 Quick Filters on the board - one for each platform. That way you simply…

Hey @J_Nova - Thanks for the additional information and clarification. Here's the deal with Backlogs and the board: The "Backlog" is just a column for the board. It happens to be off of the board as it is labeled, but you can put any status you want in there. Even multiple statues. When a card is created, it goes to the…