John Funk Community Champion

Hola, Yully. ¡Bienvenido a la comunidad de Atlassian! Puede crear un filtro para todos los problemas de un proyecto. Asegúrese de compartirlo según sea necesario. A continuación, cree un panel con un gadget de estadísticas de problemas. Luego use el estado para la estadística de emisión.

@Juan Pedro Martínez Checking again. 

Hi @Ivan Andrieiev Yes, you can always add fields to screens. Depending on which type of project you are using, you can create custom fields and add them to the screen.

My understanding was that nothing needed to be done right now - they would try to update everything first. 

You are very welcome. No - it can be associated with one and one only. 

Hi @patricio Individual users can drag columns to a different order if they want. It is not locked down like Jira Software boards. If the user drags the column back to the right order, it should stay that way for them. 

You are very welcome. 

This is an example of code you can use in a mention for a comment. [~accountid:{{issue.assignee.accountId}}]

Hi @Magdalena Zhisheva Maybe take a look at this guidance. https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-to-epic-fields-in-company-managed-projects/ba-p/1997562

Hi Lojayna - Welcome to the Atlassian Community! If you are on the task/story/issue, you should be able to select the value for the Epic in the Epic Link field, even if it is on a different project from the issue's project. 

Sure the field is called accountID and you would probably be able to access it using the user's email address. 

Can you provide a screenshot of the Board Settings > General tab?

Sorry, but I am not receiving enough information so I cannot help you further. 

You can't just stick a random user's ID in the description. It has to be related to something. 

But who is it the accountID for? The Reporter? The Assignee? Someone else?

Hi @Sinartis Support You need to use the accountId. Got to Settings > User Management Search for the user and click on the name. The accountId will be the long string of letters and numbers and dashes after /users/

Very good - did not realize you were using a Team-managed project. :-)

But what is the field you are using it for?

Hi @rbalamu2 There is no concept of a "default" Component in Jira. But you can use an Automation Rule to Edit the issue and add the Component after it gets created. Or you can add a Post Function to the Create Transition for your work flow to add the component when the issue is created. 

Hi Egor, Why have you placed the word Identifier at the end? What are you trying to see? 

Hi Sara, The Fix Version field needs to be added to the screen, also. What type of project are you using? 

Hi Jon - Welcome to the Atlassian Community! Would the Developer be the one who moves it to Done? In other words, are they the Assignee in the Done column? 

Hi Remy - Welcome to the Atlassian Community! I must say that's a strange request that the Assignee is not allowed to move the card. But I have seen stranger. :-) You will probably need a plugin like JMWE or ScriptRunner to accomplish that. 

You would need to create a custom field that captures the previous assignee by using a post function on the transition. 

Hi Simona - Welcome to the Atlassian Community! You will need to create a new workflow and place it in a new workflow scheme. Then you update the project to use the new workflow scheme. That will remove it from sharing the workflows with the other project. 

Hi @Srikanth Ganipisetty How many values to you have in the top level select? And is there anyway to group those values into smaller subset? So, I guess I should ask what type of data is in the top select? Another option might be to use ProForma forms to put in some conditional logic for the values. 

Hi Sambit, You either need to use the Checkboxes custom field type or the Select List (multiple choices) custom field type. 

Hi Briony - Welcome to the Atlassian Community! Cards that show up on boards depends on the filter associated with the board. So, you just create two different filters for the two boards to show what you want to see on each board. And then you can have a 3rd board if you like that shows all of the issues. 

Hi Neta - Welcome to the Atlassian Community! You won't be able to add a Validator when updating a field - it can only be done on a transition. 

Hi Esmeralda, Why do you need two different workflows? You can probably do it in one. Do you have a diagram that describes what you are trying to do? I am not following the written description very well.