I think this component of Requiem should behave in a different way. But I have so many mods installed, is it a really a Requiem issue or a compatibility issue on my end? Is it even an issue at all or do I only have the wrong expectations?
I bet most of you already had this feeling at some point of the Requiem journey. Sometimes a look at the manual can answer the question, but many aspects of Requiem are not yet covered in enough detail there. In these cases answering the question usually means that you have to ask it either at the Nexus Forums (or at reddit) and then it might well happen that you have to endure the "you should have searched first" sermon of a forum vigilant before you finally get your answer. Given the high influx of posts at the Nexus (on busy days we have 50-100 new posts), searching the Nexus forums can be quite cumbersome. (I recently failed to find one of my own posts and I knew what I was looking for.)
Especially annoying it becomes, if you think you found a bug and then you end up with "this was reported X times before..." after posting a question/report at the Nexus. For this particular issue, we can now offer a solution. 
After a few months of working with Atlassian JIRA (our issue tracker) and Confluence (the Wiki you are reading right now) we finally feel comfortable enough with the vast set of options JIRA has in store. Thus we decided to make our issue tracker partially public. From now on you can freely access a part of our main project in JIRA to check if the issue you experience is an already confirmed bug or if you stumbled upon something new. You can either browse this page to access the publically available issues or you can use the following links:
- The Guest Dashboard - an overview of all confirmed, not-yet fixed issues in released versions
- The Issue Index - if you want to filter the available issues with your own criterion
Please keep in mind that only a part of the project is public. At present, all our new features, tweaks and balancing issues are private. JIRA will not give you any hint that these exist at all. Thus the statistics functions for the project will yield heavily distorted results. As an example the roadmap will tell you that 11 of 11 issues are fixed for Requiem 1.8.2 while we in reality have 33 issues at the time of writing, several of them not yet finished.
Just to give you an example, here are the five most recently updated issues scheduled for the next version, fetched from JIRA at the moment you opened this blog article. This tight interconnection between Issue Tracker and Wiki is already used in the internal components of our project. Very soon we will begin to make use of it in the public parts of our Confluence as well. As a first step we intend to link the entries in the troubleshooting guide with their respective JIRA issues. This allows you to immediately see if a fix is on the way while you are browsing for the temporary solution of your issue.
Loading …
| Key | Summary | T | P | Status | Created | Updated | Affected Version/s | Fix Version/s |
|---|---|---|---|---|---|---|---|---|
| REQ-117 | The manual shows the wrong graph for the speed bonus derived from stamina |
|
|
discussion | Sep 18, 2014 | Dec 06, 2014 | Requiem 1.8.0, Requiem 1.8.1 | Requiem 1.8.2 |
| REQ-144 | False positives for new game identification |
|
|
In Progress | Oct 05, 2014 | Dec 04, 2014 | Requiem 1.8.1 | Requiem 1.8.2 |
| REQ-169 | Race descriptions don't fit character creation display |
|
|
added to changelog | Nov 03, 2014 | Nov 26, 2014 | Requiem 1.8.0, Requiem 1.8.1, Requiem 1.8.2 | Requiem 1.8.2 |
| REQ-173 | "Domination" does not decrease upkeep costs for Phantasmal Miasma |
|
|
added to changelog | Nov 06, 2014 | Nov 24, 2014 | Requiem 1.7.0, Requiem 1.7.3, Requiem 1.8.0, Requiem 1.8.1 | Requiem 1.8.2 |
| REQ-170 | Entry LvlBanditMelee1HGuard (RefID: 03DF52) is corrupted |
|
|
added to changelog | Nov 03, 2014 | Nov 20, 2014 | Requiem 1.8.0, Requiem 1.8.1, Requiem 1.8.2 | Requiem 1.8.2 |
We hope that opening our bugtracker helps to make your journey through the world of Requiem even more enjoyable. Feel free to leave your feedback.
2 Comments
Anonymous
Ogerboss, I cannot view the tracker anymore.
ogerboss AUTHOR
I assume you mean the small table here in this blog post and not the real bug tracker? If so, that was correct. We changed some internals yesterday and thus the database query for the table in this blog became invalid. To be precise, we removed the "Scheduled Version" field and decided to go back to JIRA's default interpretation of the "Fix Version". This means that issues with green status labels and Fix Version "Requiem 1.8.2" are already finished, while items with blue or yellow state labels and the same Fix Version are still work in progress, but should be part of the same release.
I have no updated the table in this blog post, thanks for pointing this out.
Add Comment