Converting an issue from one issue type to another leaves the issue with newly created issue type without the submitted date

Jayashree Shetty
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 4, 2015

If there exists an issue of issue-type "A" . If we convert this issue to another issue-type "B" we do not see the submitted date field after the creation. This is not true everytime. For some issue types we get this submitted date. Why is this inconsistency seen? 

Untitled.png

 

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 4, 2015

It sounds like you have not got the submitted date on the view screen for the new issue type, or it's hidden in the field config for that issue type, or it's not a valid field for that issue type (check context in the list of fields)

Jayashree Shetty
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 18, 2015

Thanks Nic. That is true that the new issue type has this "submit date" field but the old issue type doesn't. But there is requirement that the created date of the old issue type after conversion will be the submitted date field value for the new issue type. Since i do not see any option while"Issue Move" operation can this be still achieved by some means? Can we have a listener to do this so. I am just seeing if there's any possibility to achieve this or else if not we might now take this.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 18, 2015

Well that's the problem, the field was not there, so it can't guess what you might want in it. As you suspect, you're going to need a bit of code to update it. A listener could catch the "issue moved" event and do the update for you there.

Suggest an answer

Log in or Sign up to answer