I think you mean to hit the purple reply button at the bottom of the thread, but you seem to be replying to Phil’s replies and my replies instead.
For those reading, I ran some more tests and I think that the sorting is meant to be applied by creation date which clearly makes sense. However, on old projects that I’ve applied IDs to now, the number sequence seems to go by the creation date but not the time of the day. Other times it seems to get entirely mixed up as can be seen in the below example (I’ve noted the creation time on the right, along with the expected ID numbers in red):
Is there any way to make the new ID field the left-most column? There is actually a screen shot in Asana that appears to show it on the far left, but I can only get it to be the first of the custom fields, not the first field overall.
The screenshot is showing task row numbers. You can enable these for any project list from your profile photo (top right) > Settings > Display > Show task row numbers. Note these numbers are dynamic, based on the sort/filters applied within a section or group of custom fields; i.e. they are not fixed numbers like the custom field IDs.
I would suggest you create a new topic in the Product Feedback section for being able to place the custom ID field before the task name on the left, which others can also vote on.
A workaround is to create a custom rule with the ‘change task name’ action to include the ID custom field as a variable in the task title. You would just need to figure out the trigger for this to occur.
This is a great start, but not really what I’m looking for.
Since Projects are be definition & design time-bound, applying the ID there is too granular.
I’m looking for something more JIRA-like, applying the ID at the Team level, so that all my tasks in that team have a unique ID, and the ID lives on across projects. Arguably, even the Project would have an ID, akin to an “epic”.
Hi @Niels_Oomen, @Richard_Sather and @Phil_Seeman! Our product team has confirmed ID custom fields are generated in the order that a task was added to a project, not the creation date of the task. We have added a note at the end of our guide article to clarify this information as well!
Project A doesn’t have a custom ID set up in it.
Project B does have a custom ID set up in it.
Task 1 is created in Project A sometime in January.
Task 2 is created in Project A sometime in February.
On March 1st, Task 2 gets added to Project B.
On March 15th, Task 1 gets added to Project B.
The result:
Task 1 has an earlier creation date than Task 2. However, Task 2 was added to Project B before Task 1 was, so Task 2 will have a lower ID number than Task 1.
@Phil_Seeman that is a fair explanation. However, i was referring to tasks beloning and always have been to the same project, which had not a logical sequence.
