The digitized feature (on top of an image) is shifted as editing is finished,

[JamalNUMAN]

The digitized feature (on top of an image) is shifted as editing is finished,

I’m wondering why the digitized feature (on top of an image) is shifted when finish editing as shown in the screenshot below

What might be the issue here?

[DanPatterson_Retired]

are the coordinate systems of the map, the feature being created and the image the same including their datum

[JamalNUMAN]

Thanks Dan.

All what I did is digitizing on top of an image. Why should I have even a coordinate for the feature class or for the image?

However, with same settings, this is, of course, can be done in ArcMap with no issues as shown in the screenshot below. Just in case, the data is attached.

[DanPatterson_Retired]

did you check this in Pro? and the same conditions in map?  feature snapping? other things will explain the situation, you just need to rule out the peripheral factors

[XanderBakker]

I really wasn't expecting this comment from an experienced GIS user:

Why should I have even a coordinate for the feature class or for the image?

You really should avoid working in a GIS with a Unknown coordinate system. It is not best practices to do so. 

Here is a nice webinar on the topic:

https://www.esri.com/training/catalog/57630434851d31e02a43ef5a/working-with-coordinate-systems-in-ar... 

A coordinate system is responsible for ensuring your features display in the right location. You will learn practical guidelines for solving challenges as well as techniques to correct problems caused by unknown and missing coordinate system information.

[JamalNUMAN]

Correct. I was ignoring the fact that:

-the default coordinate system of “map” is “WGS 1984 Web Mercator” but not “unknown” as in ArcMap

-adding the first feature class to the “map” will never get it switched to the feature class’ coordinate system as in ArcMap

Assigning the same coordinate system for “map” and “feature class” resolves the issue.

We can’t forget 15 years of working in ArcMap in few days!

[DanPatterson_Retired]

I knew it had to be the coordinates system differences or lack thereof... things just don't 'jump' around.

[AlaaFlaifel]

I tried this and it worked well when I unified the coordinate systems. 

[DanPatterson_Retired]

I indicated the root of the problem earlier on.  The advice is long standing.  Never assume anything about the coordinate systems of your data and/or environment.

  'Projection on the fly' was introduced many years ago to alleviate the 'my data don't line up' issues because they were physically displaced on the map....

Now that it is here, the questions is 'my data don't line up' because assumptions are made about how the program is to work.  Just try using Define Projection tool instead of the Project tool to see what I mean