nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Identify issues created from Jira Plan

Lisa Mendonsa

Hi,

I'm trying to work out if there is a specific field or proprty that would help identify if an issue was created through a review from Jira plan.

The reason is, in Jira plan I have provided custom fields for adding commentary during the planning E.g. Open Text 1 , which would be then copied into the Description field upon issue creation. Description field is not available in Jira plan view, so thats why I have done this.

In order to automatically copy the commentary, I have an automation rule that would work in the following way:

If the issue has been created through Jira plan review, then copy the text from Open Text1 into the Description field.

And if not, ignore

Comments

Walter Buggenhout

Hi @Lisa Mendonsa

While I haven't tried this, can't you add a condition to your automation rule that checks if Description does not contain any text. If it doesn't and Open Text 1 does contain text, copy it to description?

I am not aware of any way to check if an item is created from a plan, but I would assume the above approach should provide a workaround, regardless of that.

Hope this helps!

Lisa Mendonsa

Hi Walter,

That would work but when you review items from the plan, it opens the Create Issue screen for each Issue being created. At this point, the Description field is blank but mandatory (Indicated by Red asterisk), so I was thinking people could enter a '.'

I could then check for this value in the Create Issue trigger (or something similar)

You're probably thinking why not just enter the Description as needed at the point of Review? Its because during our quarterly planning we would have potentially tens of Epics to create, the data has already been filled by the Dept leads in the Plan view and so in this screen it would be difficult to Copy paste manually (not to mention cumbersome).

I'll figure something out, I am thinking I could use a label to act as an indicator.

Walter Buggenhout

If you remove the description required restriction, the create issue popup won't appear anymore.

Creating the items in the plan view is a choice. You can also create them in Jira directly instead and they will automatically appear in your plan. But if you opt for a practice to create epics in your plan instead, it will be a more fluent experience to remove required field restrictions for fields you can't edit there.

Mendel Liang

Hi Lisa,

While I'm not sure there is a way to tell if a work item is created via a Plan off the top of my head, the description field is editable for work items in Plans. Click on the Summary to open a modal that allows you to edit the description. Hopefully this works for your use case and mitigates the need for the workaround you described.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

portfolio-for-jira

cloud-automation