From the course: Complete Guide to Jira Administration: Configuration, Management, and Automation

Unlock this course with a free trial

Join today to access over 24,600 courses taught by industry experts.

Managing project-specific settings

Managing project-specific settings - Jira Tutorial

From the course: Complete Guide to Jira Administration: Configuration, Management, and Automation

Start my 1-month free trial Buy for my team

Managing project-specific settings

“

- We just talked about schemes, which can be shared between Jira projects. Next, we'll talk about settings that are project-specific and not shared, like versions, components, and people. First, let's talk about versions in software development Jira projects. A version is a group of issues by date or time period that are deployed together in a software release. You may see versions referenced as fixed versions or releases. A related term to know is sprint. A sprint is a time-boxed iteration of focused effort. For example, for the next two weeks, the team's going to focus on a specific set of Jira issues to release. Sprints have set start dates, include a set number of issues and strict completion deadlines. Okay, back to release versions. Tom Preston Warner, inventor of Gravitar and co-founder of GitHub created the semantic versioning specification. This is a recommendation for naming versions in the format major.minor.patch. Review this recommendation at the URL shown. All versions…

Contents