Custom Field Error after migration via JCMA

[Babu, Petluri]

After Migration of project via JCMA, Analyzing pre and post migration logs.

Custom Fields is not there in our project but still showing custom fields in Pre and Post Migration summary reports.

[Deleted user · Accepted solution]

Hey there,

I couldn't find an option to find out whether a date field is larger/later than another date field.

There's an open request for this on the "Compare to" condition. You should be able to use JQL condition with smart values instead. You'll need to format the date in a JQL friendly format, something like:

"Target End date" > "{{#issue.epic.Target End A}}jqlDate{{/}}"

BUT "Target End" is nowhere to be found

You might need to make the target end field available to edit screens for your project https://confluence.atlassian.com/jiraportfolioserver/showing-portfolio-custom-fields-in-jira-software-857058481.html

If this isn't what you mean, could you post some screenshots of your rule config?

Cheers,

Mark C

[Jun_Feng_master]

Hi Mark,

Thanks for your answer.  While it's not exactly how I solved the problem but it gave me the idea to use JQL condition instead.

So for the record, my solution are:

1. Use JQL condition and put in

   "Target End A" < {{triggerIssue.customfield_10103}}

2. In the "Additional fields" area of Edit Issue, put in

   {
   "fields": {
    "Target End A": "{{triggerIssue.customfield_10103}}"
    }
   }