John Funk Community Champion

Hi Klaus, Take a look at the board filter to see what it might be excluding. Go to Board Settings > General

Hi @vshnu raj No, adding another workflow will not hurt the integration. 

No worries :-)

@Jane Yeoh 

Hi @Szymon Ptak - Did you ever get this resolved? 

It's a function inside of Automation for Jira. It returns a list of issues versus a single issue. 

I went back to basics and it worked. So that tells me there is something wrong wtih a screen or a field or something like that. Is the Epic on the same project as the task you are creating? Is the Epic Link populated at the time of creation of the task? Are the fields being copied on both the screens for the Epic and the…

Can you share a screenshot of your current rule? And what doesn't work? Do you get an error? What doees the audit log say? 

Hi Aravind, Can you provide some more details please?

Hi Angela - Welcome to the Atlassian Community! First, you need to identify what is causing the tickets to leave the board. Is it because the statuses used by the QA board are not on the Kanban Board? Does the board filter specifically not include QA statuses? 

Hi Alison - Welcome to the Atlassian Community! Remove the Resolution field from the Bug Create screen.

Initial webinar provided a good overview and path forward. Definitely worth watching. 

Hi Estelle, Try adding a Branch before you do the Edit issue action. The Branch should be Epic (Parent). Then place the Edit issue action under the branch. 

Take a look here: https://www.atlassian.com/licensing/proforma

Hi Omid, There is no funcationality in Jira Cloud that will hide fields or make fields mandatory depending on the value of another field. You can hide fields to a certain degree using ProForma Forms which should be available for your instance now. 

Hi @Eduard Jooste - Did you ever get this working? 

Hi @Mkurama No, it is not available yet. You can vote for the request and follow it here: https://jira.atlassian.com/browse/JIRAAUTOSERVER-53

This appears to be a duplicate of https://community.atlassian.com/t5/Jira-Core-Server-questions/Is-lookup-issues-support-Jira-server/qaq-p/1922282 There is no need to post a question multiple times in the Community. Answers will be given on the other post. 

You are welcome - best of luck with it!

So the Due Date field does not show up when you do an Edit within Bulk change?? It that's the case, I have NEVER seen that before. That would tell me something very weird is going on with that field. And you should open a support ticket with Atlassian. https://support.atlassian.com/contact/#/

Hi Kenneth, Is there a reason you have do to it as a post function and not use Automation for Jira? 

Hola Gonzalo - ¡Bienvenido a la comunidad de Atlassian! Las incidencias solo aparecerán como completados para los informes si las incidencias se encuentran en la última columna del tablero (extremo derecho), independientemente del estado de la incidencia.

Hi Mike, Unfortunately, the timelines view for Jira Work Management projects is still very limited. 

Hi Marcus, Jira Work Management projects are extremely limited in how cards appear on the boards. You can modify very few things, including not being able to eliminate Epics from the board or seeing the Epic link on the board. 

Hi Gerard, I don't know that you can make a change to preselect a value since it is a system field. At least, I am not aware of a way. 

Rats :-(

True - but in this case, you could change the the very end to 5#1,3#4 and it would execute tomorrow for a test. :-) BTW, I have not tested this either and have no idea if it will work. It will be interesting to see. :-)

Hi @minakshi taly - Did you ever get this done? 

I know they were to be rolling out a fix. Glad you are up and running again. :-)

No, you can't change project types. You would have to create a new project and move the issues from the existing project to the new project.