Summary field in different project

[nida ergenç]

Hi dear community,

in software project, we have post function in actions button which creates issue in service project.

But here is the question due to summary field is mandatory that im struggling, i donot want to use same summary field both projects. That's why i have created ''Task Summary" custom field and add the related screen.

But i had an this error.

and i have set summary field copy from "task summary."

Do you have any suggestions about it? 

Thanks,

[Tuncay Senturk]

Hi @nida ergenç 

If I am not getting it wrong, you're auto-filling the Summary field via post function (from task summary field) in order to create the service issue.

Even if you're copying the value into Summary, it must exist on the Create screen of the target issue type in the Service project.

Since you said you were using a post function to copy the Task Summary value into Summary field (and I assume you are not using Automation), check that the post function to copy Task Summary → Summary runs before the built-in “Create Issue” post function.

[nida ergenç]

Hi @Tuncay Senturk

i would like to explain it to more clearly with sample,

in software Project i have Project issue type.

A Project-> Summary run as “Project name”. (software project)

B->”Task Summary” explains what to be done for another team. (service desk)

when i create “End User task “in action button, where  the post function is.(JMWE-shared action not using automation), if i add Summary into create End User Task screen,it changes my current issue summary which is A Project.

[Laura Campbell]

Hi @nida ergenç 

As @Tuncay Senturk has mentioned the Summary field is required as it's one of the few standard things across any and all Jira issues. Is there a reason you don't want to use the native Summary field in the service project where you are copying issues?

[nida ergenç]

Hi @Laura Campbell ,

A Project-> Summary run as “Project name”.

B->”Task Summary” explains what to be done for another team .

Current issue summary run as my Project name,if i create issue via post function i want to use Task summary instead of Summary. Otherwise i cannot distinguish either  Project name or tasks what to be done for another team.

[Laura Campbell]

@nida ergenç If you will have multiple issues/tasks for a team to do for a same project, you should use a label, component, or custom field to hold the name of the project. That will make it easier for filtering as well, especially if your service team wants to create queues filtering by project. The summary is text, and filtering by text in Jira is not always good.

If you are putting the same text in the Summary field (a project name), all the native Jira features that display multiple issues will all look identical since they use the Summary field, and your service agents will have a harder time distinguishing between them.

I would also recommend putting the description of what the other team needs to do (task summary) into the description field. The label or custom field will help distinguish the project, and then the description can hold the description of what needs to be done.