nus-pe-bot
commented
2 months ago Team's Response
This is a valid point, however out of scope for the current version of this product. In the planned enhancements point 8 it is indicated that we will try to find a way to reuse ids for tasks that are deleted. Once that enhancement is complete, users can be given the option to reuse old ids even if the id is not near the integer limit.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: 
The enhancement in question pertains to the theoretical integer limit. The enhancement states that ids will only be reused should "the number reach close to the limit". However, my issue here has nothing to do with the ids of "deleted employees of tasks", as in enhancement #8. In fact, the hypothetical situation presented in the issue only adds tasks. The team's response is inaccurate.
The issue is that the team's current system of assigning tasks by their unique [task_id] is not scalable. Instead, I offer a suggestion that assigning tasks by their [position_id] in the display list is a better option.
Suppose a company uses this system for a year, with about ten tasks a day. The task ids will keep incrementing to
3650. When deleting or assigning such tasks, such weighty task ids are tedious to type in each time. Perhaps assigning tasks by their position in a list might be a better solution.