John Funk Community Champion

Si es administrador, haga clic en Configuración y luego en Flujos de trabajo. Luego seleccione el flujo de trabajo que necesita ver. Una vez que esté en el flujo de trabajo, debe hacer clic en la transición entre los estados.

Hi Kasper - Welcome to the Community! Typically that message from JIRA means that you have the Backlog function turned on. New issues create for that project/board will go immediately to the Backlog which is off of your board. Try clicking on the link for your Backlog to find your new issues. 

Hi Hoxell, I would check the permission scheme for Project B to see who has the capability to Browse the project. It might be based on all users and not just Project Roles. 

Hola Cecilia - Bienvenido a la comunidad! Depende de su flujo de trabajo entre los estados. Asegúrese de que haya una transición adecuada entre los dos estados para el problema que desea realizar la transición.

Hi Soporte, Where you can go from one status to the next depends on your Workflow. If the two projects use different workflows, that is probably your problem. 

Ah, I think I finally understand. When you move an issue to Done you want it to do an automatic Release. Correct? Would that be just that issue? Or when the very last issue is marked Done with that Fix Version? Not sure that is even possible. You might find more information here:…

Typically, you complete the work first (Resolution is Done) and then work is released when it is Deployed. I think the connotation is that it has been deployed by definition if it has been released. Is there a particular reason that you need to see a status of Deployed AND Released? As opposed to Done and Released?

A board can be setup to show issues from multiple projects (the issues shown are based on the underlying filter). Then you can add Quick Filters to hide certain projects independently if you like. A dashboard is going to show more aggregate data typically, but can be lists of records, also. It can also show data in the…

Hi Hermenegildo - welcome to the community! Can you be more specific for what you want to see? Is this the values of the fields after you create an Issue? If so, in the "old JIRA issue view" custom fields that do not have a value (are empty) typically do not appear in the view. You would have to click on Edit to see those…

You could add a post function for the Create transition and try to use the Update Issue Custom Field post function. But not sure if that will actually work since it is not really an update but an initial population of the field. 

Hi Claudia, You are correct, doing a Release really does nothing more than placing a value in the Fix Version field. Which then typically removes it from your board to reduce clutter. If you want to update the status you will need to either do that on a transition to your final column or create a transition on the final…

Can you send a screenshot of your Board Settings like the one Thomas provided above?

One easy trick is it create the Epic with everything you want in it but just leave it in your backlog. Then clone that ticket when you want to create a new Epic. 

Good morning AppleGirl, Maybe try this - Create a filter for each status in the process. For example, "project = XYZ and status = Open", then a filter for "project = XYZ and status = Design", etc. Then create a dashboard with the layout of 3 equal columns. Then add a gadget for Filter Results gadget for each of the filters…

Hey Amy, Can you provide a screenshot so we can see what you are looking at? And if your status is not in the list on the far right hand side, then I agree with Thomas - the project associated with the Board is not associated with the workflow that contains the statuses you are expecting to see. 

Hi Ari - Welcome to the Community! Have you looked at which issues show up on the JQL but not the CFD to see if there is anything in common? Or something that might prevent it from showing up? Maybe notice current status of the ones not showing? Can you provide one of the screenshots?

Great Idea! Looking forward to it!

Hi Saumya - Welcome to the Community! Can you provide a screenshot of what appears to be wrong? Also, why are you setting a minimum? Just curious. 

Hi Mikhail - I can at least give you my opinion. :-) If the "projects" are short lived and are spun up frequently. I would indeed use Epics instead of projects. Especially since the workflow and process is the same. We have many issues that start with one team and get handed off to another team. And then maybe another team…

Sorry, should have mentioned that we use the JMWE add-on to accomplish that. 

Hi Sumit, Yes, it is possible, and we do it a lot. Just edit the Create transition for the Sub-task (the transition from the first circle to the first status) and add a post function for each field that you want to populate on create. 

Hi Tomáš - Welcome to the Community! We use a common workflow in our organization, and it works quite well. Some caveats, though - you have to use the same statuses from the workflow in order for that to work. To don't have to use all of the statuses, but all of the ones you use need to be in the same workflow even if you…

Hi Anda - Welcome to the Community! Yes, you can create a board filter so that it shows issues from multiple projects. Something like "project in (ABC, XYZ)" or as you show above "project = ABC or project = XYZ". But in the board settings, you link the board to a single project under the location. (see screenshot). You…

Glad you like it - it has been very helpful for our organization. 

Hi Linda - Welcome to the Community! One way is to create a filter for the total issues you want to see (all issues or maybe just issues on a certain project or projects, etc.). Then create a Dashboard and add a gadget for Issue Statistics. Then for the Statistic Type, put in Assignee. That will create you a list with the…

Hi Huy, Not sure about the ER Diagram, but here is a link to the schema. https://developer.atlassian.com/server/jira/platform/database-schema/#Databaseschema-ChangeHistory

Great - glad that works for you now. Can you click on the Accept the Answer for us? Thanks!

I don't think there is a gadget that will show future steps in a workflow. Is there a reason the board will not provide the information you need?

Oh, and moving forward, if you want to track that information without an add-on, you could create a custom field for the project and update it when you create the issue. That way you have at least one former project captured.

Unfortunately, history searches are not available out of the box in JIRA. I would suggest using the API to see what you can find in the history.