Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Obsolete
-
Affects Version/s: Current Version
-
Fix Version/s: Near Future
-
Component/s: OIOIOI
-
Labels:None
Description
During the last PA there were many mostly technical discussions spread between many questions.
For example:
Contestant asked a technical question, but admin needs to know a few more details to answer properly. So contestant asked another question giving those details, but it's still not enough... And so on. I've noticed that the longest discussion during PA2014 was in 6 question-answer pairs.
Sometimes a contestant changes the title or another admin answers and it's not possible to search for previous communication.
Why not make it easier?
For example:
Contestant asked a technical question, but admin needs to know a few more details to answer properly. So contestant asked another question giving those details, but it's still not enough... And so on. I've noticed that the longest discussion during PA2014 was in 6 question-answer pairs.
Sometimes a contestant changes the title or another admin answers and it's not possible to search for previous communication.
Why not make it easier?
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.
