GitScrum
Try free

Project General Settings

Configure your project's core settings including identity, visibility, status, available features, and branding. Changes made here affect how the project appears throughout GitScrum and what features team members can access.

Overview

The General Settings tab organizes configuration into four distinct sections: Basic Information, Project Features, Branding, and Danger Zone. A Save button in the header applies all pending changes at once.

Basic Information

Private Project Toggle

At the top of the form, a toggle controls project visibility:

  • Enabled (lock icon, amber): Only invited team members can access the project
  • Disabled (open lock icon): All workspace members can view the project

Click the toggle row to switch between private and public visibility.

Form Fields

The Basic Information section includes:

  • Workspace: Read-only field showing which workspace owns this project
  • Project Name: Display name visible across all views and notifications (required)
  • Status: Current project phase - select from dropdown
  • Category: Optional grouping for organizing projects in lists
  • Project Timeline: Click to open a date range picker for start and end dates
  • Description: Text area for project goals and purpose

Status Options

The status dropdown offers three options:

  • In Progress: Project is actively being worked on
  • Completed: All work finished
  • On Hold: Temporarily paused

Project Features

Toggle individual features on or off for this project. Disabled features hide from navigation and become inaccessible. Available toggles include:

  • Time Tracking: Track time spent on tasks
  • Wiki: Collaborative documentation pages
  • Discussions: Team conversations and threads
  • Documents: File storage and management
  • User Stories: Organize work as user stories
  • Sprints: Agile sprint planning and tracking

Click any feature row to toggle its availability. Enabled features show a green checkmark and highlighted background.

Branding

Upload a custom logo that appears in project headers and navigation:

  • Click the upload area or drag an image file onto it
  • Supported formats: JPEG, PNG, GIF, WebP
  • Recommended size displays below the upload area

When a logo exists, two buttons appear:

  • Change: Upload a different image
  • Remove: Delete the current logo

Danger Zone

A clearly marked section at the bottom for irreversible actions.

Delete Project

Permanently removes the project and all associated data:

  1. Click the Delete button
  2. A confirmation modal appears with a warning
  3. Type the exact project name to confirm
  4. Click Delete to proceed

This action cannot be undone. All tasks, documents, wiki pages, and other project data are permanently deleted.

How to Save Changes

  1. Make any desired changes across sections
  2. Click the Save button in the header
  3. Wait for confirmation that changes were saved
  4. The page remains on settings with updated values

Best Practices for Project Configuration

Following these recommendations will help you maintain organized and efficient projects:

Naming Conventions

Choose project names that are:

  • Descriptive: Include the product or client name
  • Consistent: Follow a team-wide naming pattern
  • Searchable: Use terms team members will look for

Examples of good project names:

  • "Mobile App v2.0 - Client XYZ"
  • "Q1 Marketing Campaign"
  • "Infrastructure Migration 2024"

Status Management

Update project status proactively to keep your workspace organized:

  • Set projects to Completed when all tasks are finished
  • Use On Hold for projects awaiting external input or approval
  • Review In Progress projects monthly to verify they're still active

Feature Selection

Only enable features your team will actually use:

  • Fewer features mean a cleaner, more focused interface
  • Disabled features can be re-enabled anytime without data loss
  • Teams using external documentation tools may prefer to disable Wiki
  • Small projects may not need Sprints if they use simple Kanban flow

Project Timeline Tips

Setting accurate project timelines helps with:

  • Portfolio-level planning and resource allocation
  • Identifying overlapping project deadlines
  • Generating accurate progress reports
  • Managing client expectations

Update timelines when scope changes to maintain planning accuracy.

Common Configuration Scenarios

Client Project Setup

For client-facing projects, consider:

  1. Enable Private Project to restrict visibility
  2. Add a clear Description with client context
  3. Upload a Project Logo matching client branding
  4. Enable Time Tracking for billing purposes
  5. Set up Client Flow for stakeholder access

Internal Team Project

For internal projects:

  1. Keep visibility Public within workspace for transparency
  2. Enable Wiki for team documentation
  3. Enable Discussions for async communication
  4. Use Sprints if following Scrum methodology

Quick Prototype or Spike

For experimental or short-term projects:

  1. Use minimal features (just task management)
  2. Set a short Timeline with clear end date
  3. Add Description noting the experimental nature
  4. Consider skipping detailed setup if project is temporary

Troubleshooting

Changes Not Saving

If your changes don't appear to save:

  1. Check your internet connection
  2. Ensure you clicked the Save button in the header
  3. Look for error messages near form fields
  4. Verify you have Admin or Owner permissions on the project

Cannot Delete Project

Project deletion requires:

  • Owner or Admin role on the project
  • Exact match when typing the project name for confirmation
  • No active billing tied specifically to the project

Related Features

← Previous Next →