You are viewing a read-only archive of the Blogs.Harvard network. Learn more.
LDS site bugtracker » how to use

LDS site bugtracker

document bugs, float ideas, and monitor status of LDS site issues

how to use

This section talks about the basics of using this blog to report LDS site issues.

Rather than a detailed step-by-step set of instructions, the scope of this discussion is general. If you have specific questions or problems, please feel free to get in touch with Allen (arcrockATfas) anytime.

The blogging software we use is WordPress. You are encouraged to read the documentation, although most of it is written for users who are installing and managing their own blog rather than writing and editing content on another user’s blog, which is the case here. Nonetheless, the link provided above is worth browsing if you are new to blogging.

sign up with blogs.law.harvard.edu

In order to post bugs or write comments on LDS Bugtracker you need to first go to http://blogs.law.harvard.edu and sign up for blog. Anyone with a harvard.edu email address can sign up for a free account, and signing up does not mean you have to create a blog if you don’t want to. Once you have signed up, notify Allen so that you can be added as one of the blog authors.

post a bug, issue, or idea

Once you have been added as an author on LDS Bugtracker, you can login by finding the login link on one of the bugtracker pages and entering the username – password information you have set up for the site.

To report bug, write a new post with a brief description of the problem in the title and set the category of the post to “bug”. Set the category of the post likewise for issues or ideas. You can also set the category under one of existing categories (i.e. “GIF-PDF”, “URLs”, …) to help classify your entry.

Bugs and issues that are yet to be remedied will be placed under the “open” category. To see all open bugs you can select the “open” category from the navigation sidebar. Similarly, all bugs that have been resolved will be placed under the “closed” category. This method of categorization is important for monitoring the status of bugs and issues over time.

If you’re not sure how to categorize a post (the difference between “bug” and “issue” can be a little nuanced sometimes) or just simply forget to assign a category, don’t worry. Allen will figure it out.

Leave a Reply

You must be logged in to post a comment.