Configurar campos obligatorios al mover actividades a un proyecto

Question

Buenos días,

Tenemos un proyecto en Jira para gestionar la actividad del departamento,

A veces desde otros proyectos nos mueven actividades (issues).

Para garantizar la correcta gestión, necesitamos;

* Que el estado de la actividad sea siempre el mismo. En nuestro caso "Registro".
* Que se informen una serie de campos obligatorios antes de mover la actividad.

¿Es posible? En caso afirmativo ¿dónde tengo que configurarlo?

Muchas gracias

silverio.gonzalez.ext · Answer

Hi Jack,

Do you mean to say that you are moving work items from one project to another?

Yes.

The same as what? Are you saying that if an issue is moved from project A to project B you want to retain the status across the move? If so this can be done as long as your workflow is shared between the projects.

I want to always set the same status in project B, regardless of the status in project A

I'll analize the automation option.

Best regards.

silverio.gonzalez.ext · Answer

Hi Valerie,

Firstable, thank you very much for your response.

After read the documentation, I can't find how to configure the screens that appears clicking the "Move" option.

I try explain better:

1) When I click the "Move" option (to move an issue to another project) it appears a screen with 4 steps:

* Select destination Project and customer request type.
* Assign status
* Update fields
* Confirm Changes

I want modify steps 2. and 3.

In step 2. I want to force a specific status.

In step 4. I want to put some fiels that are mandatory at the destination project.

Thanks in advance

Jack Brickey · Answer

Hi @silverio.gonzalez.ext , please see below my attempt to translate and provide assistance.

Sometimes from other projects we are moved by activities (issues).

Do you mean to say that you are moving work items from one project to another?

To ensure correct management, we need;

That the state of the activity is always the same. In our case "Registration".

The same as what? Are you saying that if an issue is moved from project A to project B you want to retain the status across the move? If so this can be done as long as your workflow is shared between the projects.

That a series of required fields are entered before moving the activity.

You cannot place requirements on a "move" action. You could create an automation rule that would inspect the fields after the move and notify an appropriate person.