Project Dune:Features

From PDune

Contents 1 Feature Descriptions 1.1 Access to pDune 1.2 Issues 1.3 Customers 1.4 Inspections 1.5 SCRUM tasks 1.6 Timesheets 1.7 Documents 1.8 Estimates 1.9 Test management 2 Screenshots

Feature Descriptions

Access to pDune

• Anonymous access. A special profile is set up where you can configure access permissions and projects that anonymous users have access to.
• Log in with OpenID. You can register on any OpenID provider and then register a special OpenID account on the server. OpenID users can be configured with their own access permissions.
• Log in directly through a cookie through the "remember me" functionality.

Issues

With the issue management module, you can:

• Create issues with title, description, severity, status, replication details on projects that the user has access to.
• Manage issues by changing severity, status. Add CCB or CSR comments and resolution details.
• Retrieve issues:
  • List issues and filter them on various properties. Adjust the size of the list dynamically, stored as a user preference.
  • Report on a filtered collection of issues by means of a simple issue list or an issue summary.
  • Search issues through a full-text search. All issue text fields and journal entries are indexed (not "text" attachments).
• Workflow tunning, if necessary:
  • code your own logic to manage the workflow and assignment rules of status, severity and owner changes of an issue.
  • code your own breakout class that generates your issue references for you.
• Add journals and attachments to issues if required.
• Associate issues with one another in different ways and output a report of the issue hierachy.
• Manage projects. This is where the details to the repository are configured for inspections in the browser.
• Manage releases. The releases are planned through this section. Releases contain scope statements that determine the scope of the release.
• Associate issues with a scope statement of a certain release. This develops the expectation in the system that those issues will be resolved as part of that release.
• Organize and document meetings.
• Manage your users.
• Notifications:
  • Get notified by email when issues change through the "subscribe" button.
  • Atom feed for most recently added journal entries.
  • Atom feed for most recently modified incident.

Customers

With the customer management module, you can:

• List customers
• Edit customer details. Add/edit contacts. Add/edit addresses.
• Add journal entries for the customer for relationship management.
• Manage helpdesk emails. Emails can be sent to a special CRM inbox that is regularly polled by the system. Based on the 'From' email address, the email is analyzed. You can then auto-create an issue on that customer and request the allocation to a particular release of that issue.

Inspections

With the inspection module, you can:

• Inspect binary elements of a repository commit and make your comments
• Inspect source code through the browser and add your comments. Inspection comments are classified by severity, type and the phase in which the issue was introduced.
• Always have access to inspections undertaken earlier
• Always have direct overview to pending inspections for your current release.

SCRUM tasks

With the SCRUM task management module, you can:

• List and filter tasks by release, project, issue and owner.
• Edit tasks and provide detailed estimates on task completion
• Create new tasks for a given issue.
• Manage your tasks from a "SCRUM" like detail board. You can see the tasks that are allocated to different users and those that are not allocated. Edit the tasks directly from the planning board.

Timesheets

With the timesheet management module, you can:

• See your registered time by day, week or month.
• Navigate through the calendar by day, week or month.
• Timesheet items are always associated to your tasks that are set up in Scrum task management.
• Export timesheet information through a batch process. This also locks the timesheet items and sets a new processing date for that project.
• Project managers can review the times that are booked against the project and approve each item separately.
• Project managers can also reject the remaining items on the list and provide a reason for the rejection.
• A timesheet notification job is set up by default that mails out reminder emails to complete and submit timesheets every friday at 16:00. (time can be adjusted easily).
• When timesheets are approved, rejected or sent for approval, emails are sent to the people involved.

Documents

With the document management module, you can:

• Manage the text and versions of documents.
• Add new CSS / DocBook stylesheets that make up your document template.
• Write document paragraphs (elements) in the browser using a rich text editor and associate those elements with issues in your system.
• Export full documents to PDF.

Estimates

With the estimate management module, you can:

• Start new estimates or copy from existing ones, calculating effort and time using the Cocomo II estimate model.
• Divide your estimates in modules.
• Tweak your environmental and project-specific settings for each estimate.
• Save the estimates to the database and compare them to the timesheet later.

Note that the estimate management module is very new, subject to change and lacking loads of useful features. It's preview mostly.

Test management

With the test management module, you can:

• Write test cases per project in RichText format.
• Start a new test run per release with the current active test cases for that project.
• Register the outcome of test results online. The test case itself is available as a hidden panel that can be visualized with a click of the mouse.
• Reopen previously registered issues from the same window
• Report on the status of the latest test run for a certain release.

Screenshots

Here are various screenshots of project dune in action:

screenshots

A list of issues on screen. The personal filter is recorded and reusable across sessions. The search function is clearly visible along with the option to modify the number of rows.	Viewing an issue created. Notice that fields are not modifiable. See button at left to set the screen in editing mode.	Editing an issue.	Adding a meeting. Notice action buttons.
Editing a release. Notice the scope statements, which describe the scope of that release. Important for scope management.	Generating some reports. Only reports that your user has access to will be visible.	How much was initially estimated, how did that translate into the task planning and how much effort was eventually burned?	Are we ready for release yet?
Reporting on the timesheeet according to some filter settings	You can create complex hierarchies between issues and visualize them this way	Editing a user	Atom feeds to keep up-to-date with modified incidents and journals
Listing a customer	Editing a customer. Notice the helpdesk emails that can be received by IMAP or POP3 and automatically allocated against a customer. You can then turn them into issues at the click of a button	Inspection source code through the browser	Reporting on inspections done. This can be done at any point in time, since all inspection data is stored in the database.
Task management a la SCRUM	Task burndown graph filtered on a single release	Product burndown graph filtered on a single release	The timesheet with the day perspective
The timesheet with the month perspective	Tweaking estimate scale factors.	Calculating the results of the estimate.	Listing the test runs.
Registering the test results for a certain test run. This allows you to create a new issue from the same screen, greatly reducing the time necessary to execute test runs.