Details
-
Type: Improvement
-
Status: Closed
-
Priority: Minor
-
Resolution: Won't Fix
-
Affects Version/s: Current Version
-
Fix Version/s: None
-
Component/s: OIOIOI
-
Labels:None
Description
We have many places around the system, where some submission status is defined:
- https://github.com/sio2project/oioioi/blob/master/oioioi/contests/models.py#L229 ,
- https://github.com/sio2project/oioioi/blob/master/oioioi/submitsqueue/models.py#L13 ,
-SIO-1293 ,
- ?????
This leads to many problems, like:SIO-1482 . Therefore, I think it would be a good idea to have one common place for submissions statuses and to keep them all hardcoded there.
- https://github.com/sio2project/oioioi/blob/master/oioioi/contests/models.py#L229 ,
- https://github.com/sio2project/oioioi/blob/master/oioioi/submitsqueue/models.py#L13 ,
-
- ?????
This leads to many problems, like:
Activity
- All
- Comments
- History
- Activity
- Transitions
- Commits
Connect your code to JIRA
Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.Git & Mercurial in the cloud
Collaborate across unlimited private code repositories.
Git behind the firewall
Manage and collaborate on Git repositories behind a firewall.
Browse and search code
Browse, search, and track source code repositories.