Archives: Helps

Bug Issue Type in Orangescrum Cloud helps teams differentiate between various kinds of reported items — such as bugs, improvements, feature requests, or general queries.

By defining specific issue types, you can manage work more efficiently, prioritize development, and generate accurate reports for QA and product analysis.

Example: When a user reports an “API timeout,” you can log it as a Bug, while a suggestion to “Add export to PDF” can be logged as an Improvement.

Why Use Issue Types

• Organize issues logically — separate bugs, tasks, enhancements, and queries.
• Improve reporting — generate more accurate defect and improvement metrics.
• Simplify tracking — quickly filter and assign items based on type.
• Align teams — ensure QA, dev, and product teams speak the same language.

Accessing Bug Issue Type Settings

1. Go to Settings → Bug Settings → Issue Type.
2. You’ll see the existing default issue types such as Bug, Improvement, and Query.
3. You can activate, deactivate, or add new custom issue types anytime.

Default Issue Types

Issue Type	Description	Example
Bug	A defect or error that breaks functionality or causes unexpected results.	Broken link, calculation error, crash on save.
Improvement	A request to enhance existing functionality.	Optimize dashboard speed, update email template.
Query	A question or clarification request that does not indicate a product fault.	“How does this filter work?”

You can also create additional issue types such as Feature Request, Enhancement, or Change Request to suit your project workflow.

Adding a New Issue Type

1. Click + New Issue Type (top-right corner).
2. Enter a clear Issue Type Name in the field (e.g., Enhancement, Task, Feature Request).
3. Click Add to save it.
4. Your new type will now appear in the list and can be selected when logging bugs or issues.

Editing or Deleting an Issue Type

• To Edit, hover over the issue type name and click the icon.
• To Delete, click the icon to remove it from your configuration.
• Deleting an issue type will not erase the associated issues but will unlink the classification.

Tip: Keep your issue types minimal (3–6) to avoid confusion and maintain reporting clarity.

Bug Category in Orangescrum Cloud allows you to classify and organize defects based on specific modules, functionalities, or areas of your project.

By grouping bugs under meaningful categories—such as UI/UX, Database, Integration, or API Errors—you can streamline triage, assign the right team members, and analyze recurring issues more effectively.

Example: You can create separate categories like “Login Module,” “Payment Gateway,” or “Dashboard Reports” to quickly locate and manage defects in those sections.

Why Use Bug Categories

• Improve visibility: Quickly identify which area of the project the issue belongs to.
• Streamline assignment: Assign issues to the right functional or technical owner.
• Enhance reporting: Track recurring problems within a specific feature or module.
• Speed up resolution: Reduce back-and-forth communication by clearly defining ownership.

Accessing Bug Category Settings

1. Navigate to Settings → Bug Settings → Category.
2. You’ll see an empty list if no categories exist.
3. From here, you can add new categories or manage existing ones.

Creating a New Bug Category

To create a category:

1. Click + New Bug Category (top right corner).
2. Enter a Category Name in the pop-up window.
   • Example: UI Design, Database Query, API Failure.
3. (Optional) Check Create another if you want to add multiple categories continuously.
4. Click Add to save your new category.

Your new bug category will now appear in the list and will be available for selection when logging new issues or editing existing ones.

Editing or Deleting a Category

• To Edit, hover over the category and click the icon to rename it.
• To Delete, click the icon to remove categories no longer in use.
• Any deleted category will be unlinked from existing bugs, but the bug records themselves will remain intact.

Tip: Keep your category names short and descriptive so team members can quickly identify where an issue belongs.

Bug Severity in Orangescrum Cloud helps you classify how critical or impactful a bug is to your system, functionality, or end users.

It indicates the technical seriousness of a defect — whether it blocks key features, causes minor inconvenience, or is simply cosmetic.

By defining bug severities, teams can prioritize fixes effectively, ensure faster turnaround for critical issues, and maintain product quality through consistent classification.

Example: A crash on the login page would be tagged as High Severity, while a typo in a tooltip may be Low Severity.

Why Define Bug Severity

• Prioritize fixes smartly — focus first on issues that affect business-critical functionality.
• Standardize QA reporting — ensure all team members use consistent severity levels.
• Improve visibility — generate better defect analytics and release dashboards.
• Optimize time management — align developer effort with real system impact.

Accessing Bug Severity

1. Navigate to Settings → Bug Settings → Severity.
2. You’ll see a list of existing severity levels such as Trivial, Minor, Medium, High, etc.
3. You can enable, disable, or add new severity types as needed.

Default Severity Levels

Severity	Description	Typical Example
Trivial	Very minor issue with no functional impact.	Spelling error, UI alignment.
Minor	Small problem that does not block normal operation.	Misaligned label, minor color issue.
Medium	Noticeable defect affecting a secondary feature.	Sorting issue in a report, minor data mismatch.
High	Major issue affecting primary functionality but with a workaround.	Broken workflow, incorrect calculations.
Critical (custom)	Severe defect that blocks core functionality or causes system failure.	Application crash, data corruption.

Note: Severity levels can be customized to match your organization’s QA or release policies.

Adding a New Severity Level

1. Click + New Bug Severity (top-right corner).
2. Enter a clear and concise Severity Name (e.g., Critical, Blocker, Cosmetic).
3. Click Add to save your new severity.
4. The new level will now appear in your list and be available while reporting bugs.

Editing or Deleting Severities

• To Edit, hover over a severity and click the edit icon to rename or update it.
• To Delete, click the trash icon to remove unwanted levels.
• Changes are applied instantly across all projects using that configuration.

Note: Removing a severity will unassign it from existing bugs but will not delete those bug records.

The Bug Settings section in Orangescrum Cloud gives you full control over how issues and bugs are categorized, tracked, and resolved within your projects.

Here, workspace admins can define custom attributes — such as Severity, Category, Issue Type, Root Cause, and Resolution — to standardize bug reporting and ensure consistency across teams.

By tailoring these settings to your workflow, you can streamline your QA process, improve collaboration between testers and developers, and gain better visibility into defect patterns and priorities.

Example: QA teams can classify bugs by severity (Critical, Major, Minor), track affected versions, and record root causes to prevent recurring issues.

Why Use Bug Settings

• Standardize issue tracking across all projects and teams.
• Prioritize effectively with clearly defined severity and categories.
• Enable detailed analysis by linking bugs to causes, versions, and resolutions.
• Customize your workflow to match your QA, UAT, or production process.
• Improve reporting accuracy for bug trends, fix rates, and release quality.

Accessing Bug Settings

1. Go to Settings → Bug Settings.
2. You’ll find configurable sections such as:
   • Severity – Define the impact level of a bug.
   • Category – Classify bugs based on functionality or module.
   • Issue Type – Specify the type of defect (e.g., Bug, Enhancement, Request).
   • Activity Type – Track related test or development activities.
   • Phase – Identify which stage (UAT, QA, Production) the issue occurred in.
   • Root Cause – Record the underlying cause for process improvement.
   • Fix Version / Affect Version – Link defects to release versions.
   • Origin – Capture where the issue originated.
   • Resolution – Document how the issue was fixed or handled.

The Timesheet Settings section in Orangescrum Cloud allows you to configure who approves team timesheets within your workspace.

This ensures that all logged hours — whether for tasks, projects, or clients — go through an approval process before they are finalized for reporting or invoicing.

By defining Timesheet Approvers, organizations can maintain accuracy, accountability, and transparency in their time tracking and billing operations.

Example: A project manager can be set as the approver for their team’s timesheets, ensuring all time entries are reviewed before invoicing the client.

Why Use Timesheet Settings

• Ensure accuracy: Validate work hours before billing or payroll.
• Assign approvers: Designate who reviews and approves timesheets per project.
• Maintain accountability: Keep track of who approved or rejected time entries.
• Improve reporting: Only approved timesheets are included in cost and resource reports.

Accessing Timesheet Settings

1. Navigate to Settings → Company Settings → Timesheet Settings.
2. You’ll see a list of all existing approvers, along with their email addresses, approval status, and pending timesheets.

Understanding the Interface

Field	Description
Name	Displays the approver’s name and profile picture.
Email	The approver’s registered email address in the workspace.
Pending Approvals	Number of timesheets awaiting review from that approver.
Status	Indicates whether the approver is Active or Inactive.
Action	Allows you to edit or remove an approver.

Adding a Timesheet Approver

1. In the Select Approver field, start typing the user’s name.
2. Select the desired user from the dropdown list.
3. Click Add Approver.

Once added, the user will appear in the list of active approvers and will begin receiving timesheet approval requests for relevant team members.

Note: Only Admins or authorized users can manage approvers in Timesheet Settings.

Managing Approvers

You can update, activate/deactivate, or remove approvers anytime:

• Edit Approver: Update details or reassign approval rights.
• Deactivate: Temporarily disable an approver without removing them.
• Delete: Permanently remove a user from the approver list.

All changes reflect instantly across ongoing timesheet submissions.

Timesheet Approval Flow

1. A team member submits their weekly or daily timesheet.
2. The assigned approver receives a notification.
3. The approver reviews the entries, validates hours, and approves or rejects them.
4. Once approved, the time logs are automatically marked as billable (if applicable).

This workflow helps maintain precision in both client billing and internal project cost tracking.

With Timesheet Settings in Orangescrum Cloud, you can ensure that every logged hour is validated, every project remains transparent, and every invoice is backed by verified data.

The Project Template feature in Orangescrum Cloud allows you to create new projects quickly using predefined frameworks.

Instead of building each project from scratch, simply choose a template that matches your workflow — such as Scrum, Kanban, Bug Tracking, or Content Management.

Each template comes with built-in structures like task types, statuses, workflows, and permissions — helping your team get started faster and stay consistent across projects.

Example: A marketing team can start with the “Content Management” template to plan campaigns, while a software development team can use “Scrum” for sprint-based planning.

Why Use Project Templates

• Save setup time — start projects instantly with pre-defined structures.
• Maintain consistency — ensure all projects follow your standard workflows.
• Built-in best practices — each template includes optimized settings for different project types.
• Customizable — edit or extend any template to match your organization’s needs.

Accessing Project Templates

1. Navigate to Settings → Company Settings → Project Template.
2. You’ll see a library of available templates categorized by workflow type.
3. Each template card displays a title, description, and a “Create Project” button.

Available Templates

Template Name	Description	Ideal For
Simple	Do more than just “manage” — organize, assign, and track tasks easily.	General project management
Scrum	Create backlog items, manage sprints, and track progress visually.	Agile software teams
Kanban	Visualize work progress on boards with customizable statuses.	Continuous delivery teams
Bug Tracking	Capture, prioritize, and resolve issues using a structured workflow.	QA and testing teams
Content Management	Plan and release content with review and approval steps.	Marketing, editorial teams
Task Tracking	A minimal To-Do–based project structure for small teams.	Personal or lightweight team projects
Recruitment	Manage hiring stages from job posting to onboarding.	HR and recruitment teams
Procurement	Track procurement from RFP to order completion.	Operations and purchase departments

Each template is designed to fit specific business use cases while remaining flexible enough to customize.

Creating a New Project from a Template

1. Choose a template that suits your workflow.
2. Click “Create Project.”
3. Enter your project details (name, start/end date, members, etc.).
4. Review the predefined setup — including workflow, task types, and permissions.
5. Click Save to launch your project instantly.

Your new project will now include all the template’s preloaded configurations — ready to go from day one

Customizing Project Templates

You can tailor existing templates or create new ones to fit your company’s unique processes.

Common customizations include:

• Adding new task types or labels
• Adjusting workflow statuses
• Editing automation rules
• Assigning role-based permissions

Tip: Use custom templates for repeating project types like client onboarding, product releases, or marketing campaigns.