Source Code Management

From BC$ MobileTV Wiki
(Redirected from JQL)
Jump to: navigation, search

Source Code Management (commonly abbreviated SCM, also called Source Control Management) is a term used to describe the software and/or principles and practices used to manage software engineering, research, and development efforts. SCM may include other software engineering and testing concepts for example documentation, version management, load balancing/testing, unit testing, integration testing, code coverage, bug tracking/management and code quality in general.


Semantic Versioning

Semantic Versioning is a standard numbering/naming convention for software and/or hardware products.


[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]


[13] [14] [15]


Centralized Version Control




Distributed Version Control




GIT is a new source code management tool for managing repositories in a very similar but (reportedly) speedier and more user-friendly manner than CVS or SVN. It is also (reportedly) more similar to SVN.

Monorepo strategy

[19] [20] [21] [22] [23] [24] [25]

Polyrepo strategy

[26] [27] [28] [29] [30] [31] [32]

Dependency Management

[62] [63] [64] [65] [66]

Artifact repository


[68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78] [79] [80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90] [91] [92] [93] [94] [95] [96] [97] [98] [99] [100]



Tattletale is a command-line tool that can run through a project's Maven dependencies, generate a dependency graph and determine any collisions or inconsistencies between versions so you can upgrade your dependencies intelligently rather than "in the dark / hoping for the best". Any breakages in expected parameters, object data types, depecrated classes, etc are pointed out so you can upgrade with confidence that your codebase will be in tact (or what needs to be changed in order to upgrade successfully).

Release Management

Release management is a relatively new but rapidly growing discipline within software engineering. Organizations that have adopted Agile methodologies are often facing a need for much higher quantities of releases over the lifecycle of a given project/system/application. With the increasing popularity of Agile development a new approach to software releases known as Continuous Delivery and culture of collaboration between key technology and business teams known as DevOps is starting to influence how software transitions from development to a release, with varying yet increasingly critical and complete levels of automation required to support the ever-growing demands.

[108] [109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119]

Definition of Done

Definition of Done (commonly abbreviated DoD) is a consensus, factual, un-opinionated, transparent and clearly communicated target objective state at which a given feature, functionality, code or technical system is considered to be completed and "signed-off" (as in, if delivered by a third party then that party would have been paid in full or expect to receive payment within the agreed procurement timeframe, i.e. "30 days to pay invoice").


Feature Flags are configurable properties and corresponding logic checks on the activation status that modify the behaviour of an application by toggling features on and/or off, for the purpose of more granular control over rollout of features by environment and/or individual server(s) within an environment.

[121] [122] [123] [124] [125] [126] [127] [128] [129] [130] [131] [132] [133] [134] [135] [136] [137] [138] [139] [140] [141] [142] [143] [144] [145] [146] [147]

Code Reviews

Code Reviews are systematic examinations (also commonly referred to as peer reviews) of computer source code, designs and/or specificationos.[148]

Static Code Analysis


Pull Request
Continuous Merge


Application Lifecycle Management (commonly abbreviated ALM).

Defect Management

ConOps = Concept of Operations, or "Concepualization" phase

A defect (also commonly referred to as a bug or issue) is anything that prevents you from using a piece of software as intended (and potentially could be extended to include anything that stops you from using a piece of software the way you'd like to, however most companies/methodologies will classify this as a new feature/functionality request and relegate bugs to errors & imperfections in the existing system).

Defect Management is the process an organization or team creates and follows around tracking, prioritizing and fixing defects/bugs. Most commonly you want to prioritize fixing any bugs which stop you from testing, or your users from using the system. It is important to note that bugs do not have to be code-related. The following a list of potentially non-code related bugs:

  1. job abends
  2. document errors
  3. error messages on screen
  4. information appearing on screen you think should not be there
  5. information not appearing on screen that you think should be there
  6. environment issues
  7. system taking too long to respond
  8. human-error in usage of system or data entry
  9. data problems introduced independently of code (i.e. by external end-user, internal tester, etc)
  10. errors introduced to the building or deployment process (log or config files no longer being set, irrelevant warning/error messages that aren't true errors polluting the logs, etc)
  11. functionality that works but deviates somehow from the design/specifications
  12. anything that does not "look right" to you, based on agreed upon designs/wireframes

It is crucial to be able to prioritize the business significance as well as rank the severity (impact) of the defect on the functionality of the overall solution and integrated systems/interfaces. Depending on the type of bug, you want to ensure that it is clear which one is most impactful to resolve next. No software is truly perfect and "bug-free" but near-perfect "approaching zero-bug" systems are still a good goal to strive for.

[154] [155] [156] [157] [158] [159] [160]

Issue Trackers


JIRA (short for go-ji-ra, in Japanese pronunciation) the "tongue-in-cheek" name comes from the fact that the tool is designed to tame and get under control even the most unwieldy monsters of projects run-amuck. It provides Issue Tracking (Enhancements, Operational Tasks, Sub-Tasks, etc), Defect/Bug Tracking, Agile Project management (Backlogs, Boards, Epics, User Stories, etc) and reporting on projects, teams/members and release planning.

[168] [169] [170] [171] [172] [173] [174] [175]

[176] [177] [178] [179] [180] [181] [182] [183] [184] [185] [186] [187] [188] [189] [190] [191] [192] [193] [194] [195] [196] [197] [198] [199] [200] [201] [202] [203] [204] [205] [206] [207] [208] [209] [210] [211] [212] [213] [214] [215] [216] [217] [218] [219] [220] [221] [222] [223] [224] [225] [226] [227] [228] [229] [230] [231] [232] [233] [234] [235] [236] [237] [238] [239] [240] [241] [242] [243] [244] [245] [246] [247] [248] [249] [250] [251] [252] [253] [254] [255] [256] [257] [258] [259] [260] [261] [262] [263] [264] [265] [266] [267] [268] [269] [270] [271] [272] [273] [274]

Microsoft Lists

Sonar is an open platform to manage code quality. As such, it covers the 7 axes of code quality:

  1. Duplications
  2. Unit Tests
  3. Complexity
  4. Coding Rules
  5. Potential Bugs
  7. Architecture & Design

Trac is an enhanced wiki and issue tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. Our mission is to help developers write great software while staying out of the way. Trac should impose as little as possible on a team's established development process and policies.

It provides an interface to Subversion (or other version control systems), an integrated Wiki and convenient reporting facilities.


GForge® Advanced Server GForge AS is completely rebuilt to make a modern, extensible platform with an intuitive interface that ties together a huge toolset, from Source Code Management (SCM) to extremely customizable Trackers, Task Managers, Document Managers, Forums, Mailing Lists. All of these are controlled by a centralized permission system and maintained automatically by the system.


Bugzilla is server software designed to help you manage software development.


16bugs lets you manage your bugs from a simple and productive interface. From a single account you'll be able to track your activity on the whole 16bugs network: companies you own, bugs assigned to you and bugs you sent. If you've ever tried one of the many bug tracking solutions available around, you know how complex and unfriendly they tend to be.

16bugs was born because the company behind it believe bug tracking should be an easy and unobtrusive task. Not every project needs a plethora of functions which in most cases brings only confusion in both the developers and in the people who want to submit a bug.


Distributed Bug/Issue Tracking

[279] [280] [281] [282] [283] [284] [285] [286] [287] [288]




External Links

[289] [290] [291] [292] [293] [294] [295] [296] [297] [298] [299] [300] [301] [302]


  1. Semantic Versioning for Dummies:
  2. Ease the Pain With Versioning and Releasing:
  3. DevOps -- Semantic Versioning Simplified:
  4. Java’s Time-Based Releases:
  5. Spring framework moves from "named/themed" releases to to Semantic Versioning:
  6. Stamping Version Number and Build Time in a Properties File with Maven:
  7. Reading my own JAR's Manifest:
  8. Maven Cookbook -- How To Add Build Time To A JAR Manifest: (with "antrun" Maven plugin)
  9. Displaying the build time-stamp in an application: (options that don't require "antrun")
  10. Get Maven artifact version at runtime:
  11. Retrieve version from maven pom.xml in code:
  12. How to Avoid the Java FileNotFoundException when loading Resources:
  13. Generating a project changelog using Git log (1-liner):
  14. Auto-generating a changelog from git history:
  15. A Beginner’s Guide to Git — What is a Changelog and How to Generate it:
  16. wikipedia: AccuRev SCM
  17. What is a one-sentence explanation of how Accurev works?:
  18. A Guide to Branching in Mercurial:
  19. How Google manages open source:
  20. Monorepo — the Google way to do CI/CD:
  21. You too can love the MonoRepo:
  22. Advantages of monorepos:
  23. Misconceptions about Monorepos (Monorepo != Monolith):
  24. Why might (and might not) a project/company use a monorepo?:
  25. Guide to Monorepos for Front-end Code:
  26. Trunk-based development could be either easier or more harmful in Monorepos:
  27. Advantages and Disadvantages of a Monolithic Codebase:
  28. In Defense of Not-Invented-Here Syndrome:
  29. We’ll Never Know Whether Monorepos Are Better:
  30. The issue with Monorepos:
  31. Dangers of Monorepo Projects:
  32. Monorepo is a bad idea:
  33. Maven tutorial (E-BOOK):
  34. Maven for building Java applications - Tutorial:
  35. How to create a Web Application Project with Maven:
  36. Gradle vs. Maven for dependency management & build automation:
  37. What is NPM?:
  38. Installing Node.js via (OS) package manager:
  39. Installing & updating NPM:
  40. A Beginner’s Guide to npm — the Node Package Manager:
  41. Beginners Guide -- Getting Started with Bower Package Manager:
  42. Ruby6 -- grems - Basics:
  43. Installing Python on Windows:
  44. Linux - Install pip Client To Install Python Packages:
  45. Installing Python Modules:
  46. How do I install pip on Windows?:
  47. Given the name of a Python package, what is the name of the module to import?:
  48. A non-magical introduction to Pip and Virtualenv for Python beginners:
  49. How to download and install Python Packages and Modules with PIP:
  50. What is PHP Composer?:
  51. A Beginner’s Guide To Composer:
  52. PHP Tutorial -- Getting Started with Composer:
  53. Easy Package Management With Composer:
  54. MSDN - Create and publish a package:
  55. Using ActivePerl PPM:
  56. MSDN - Use a NuGet package:
  57. MSDN - Consume NuGet packages in Visual Studio:
  58. Using NuGet Packages:
  59. Could Docker replace package management?:
  60. How to manage docker image dependencies (maintainance):
  61. Don't download the internet. Share Maven and Ivy repositories with Docker containers:
  62. “Vendor Everything” -- libraries and dependencies:
  63. (by Google): | API
  64. Introducing the Open Source Insights Project:
  65. Maven dependencies - explored with Neo4J (then turned into a Google project): (built using "Neo4j sandbox")
  66. Google to Neo4j:
  67. Muse is now Sonatype Lift!:
  68. Nexus Repository Enterprise -- Repository Manager Pro features:
  69. Nexus - 2 minute challenge (series of E-Learning videos):
  70. Nexus Repository OSS & Nexus Repository Pro -- Search API - Downloading the Latest Version of an Asset:
  71. Sonatype Nexus -- Repo manager 3.x - Maven repositories:
  72. Jenkins -- Publish Maven Artifacts to Nexus OSS Using Pipelines or Maven Jobs:
  73. How to configure Sonatype Nexus repository with Maven?:
  74. How to integrate Nexus with Jenkins for simpler builds:
  75. Configuring Nexus for Secure Access to Maven Central:
  76. How to configure a proxy repository to "":
  77. How to configure pom.xml file to use Nexus Repository manager:
  78. Developing with Eclipse and Maven -- Browsing and Manipulating Maven (Nexus & other artifact) Repositories:
  79. Using Nexus 3 as Your Repository -– Part 1 - Maven Artifacts:
  80. Using Nexus 3 as Your Repository –- Part 2 - Maven Artifacts:
  81. Node Packaged Modules and npm Registries: (rough overview of npm registries in Nexus)
  82. npm-package.json -- Specifics of npm's package.json handling when referencing external packages/dependencies: (how to point packages to BitBucket or possibly Nexus)
  83. Setting up a Secure, Private Nexus Repository: (this one’s for Maven but getting closer)
  84. Nexus Repository Manager - Proxying Maven and npm Quick Start: (proxying maven & npm, nice video at least maybe this would suffice but missing technical details in a write-up)
  85. Publishing private NPM packages to Nexus: (different approach using Docker, but closer to the kind of guide I’m looking for)
  86. Nexus -- NPM registry -- proxying/mirroring:
  87. Dependency Management in Scrum:
  88. Jenkins plugins -- Nexus Platform plugin:
  89. Nexus Platform Plugin for Jenkins:
  90. Nexus Sonatype workflow automation within Jenkins Pipelines:
  91. How to publish Java build artifacts to Nexus using Jenkins & Maven:
  92. Workflow Automation - Publishing Artifacts to Sonatype Nexus using Jenkins Pipelines:
  93. Publishing Artifacts to Sonatype Nexus Using Jenkins Pipelines:
  94. Integrating Maven and Nexus for Continuous Delivery with Jenkins:
  95. Jenkins Nexus Integration - How to integrate Sonatype Nexus with Jenkins - Upload artifacts from Jenkins to Nexus repository:
  96. Publishing Artifacts to Sonatype Nexus using Jenkins Pipelines:
  97. Setting up a CI/CD pipeline with Jenkins, Nexus, and Kubernetes:
  98. Continuous Delivery with Sonatype Nexus, Jenkins and the Cloudogu EcoSystem:
  99. Are You Still Wondering About Dependency Confusion Attacks?:
  100. Sonatype Releases New Nexus Firewall Policy to Secure Software Supply Chains from "Dependency Confusion" Attacks:
  101. Zen & the art of NPM artifacts:
  102. wikipedia: Software_release_life_cycle#Release_candidate (RC)
  103. wikipedia: Software_release_life_cycle#General_availability_(GA) (GA)
  104. wikipedia: Software_release_life_cycle#Release_to_manufacturing_(RTM) (RTM)
  105. wikipedia: Software_release_life_cycle#Release_to_web_(RTW) (RTW)
  106. wikipedia: Software_release_life_cycle#End-of-life (EOL)
  107. Microsoft Operations Framework:
  108. Magic Quadrant for Application Release Automation (2016):
  109. Are there any words I can use to disambiguate “biweekly”?: (fortnightly=every 14 days, semi-weekly=twice per week)
  110. What Does It Mean to Be Potentially Releasable?:
  111. The Release Manager is Dead. Long Live the Release Manager!:
  112. The Forrester Wave™ -- Continuous Delivery and Release Automation, 2018:
  113. Automated "release notes" for Android:
  114. PHP Conventional Changelog - Generate changelog and release notes from commit:
  115. Releasing Often Helps With Analyzing Performance Issues:
  116. Deploys at Slack:
  117. The Pain of Infrequent Deployments, Release Trains and Lengthy Sprints:
  118. Why Your Fast Release Cycles are Wasting (rather "may waste" if not done right) Precious Developer Time:
  119. Decoupling Deploy from Release -- An Essential Foundation:
  120. LaunchDarkly alternatives: | |
  121. Stop Drowning in Feature Requests, Start Delivering Real Value:
  122. Rapid Deployment of New Subscription Billing with Flag-Driven Development:
  123. How CloudBees Uses Feature Flags to Gain a Competitive Edge:
  124. Every day is launch day - How billions of FeatureFlag events helped us roll out a new Jira:
  125. Feature Branching your way to greatness: (suggest to combine Feature Flags with MOST Feature branches)
  126. Atlassian guide to FeatureFlags:
  127. Feature Branching .vs. Feature Flags - choose the right tool for the job:
  128. Martin Fowler blog - Feature Toggles: (original guest post by Pete Hodgson)
  129. Martin Fowler's own on Feature Toggles and their appropriate usage:
  130. Feature Flags, what are they and why should I care ?:
  131. DZone – Refcard #305 - Controlling Features With Feature Flags:
  132. 10 Ways to Use Feature Flags:
  133. Tutorial on using Feature Flags in Java (complete example):
  134. LaunchDarkly -- The definitive guide to feature management:
  135. Feature Branching Using Feature Flags:
  136. 5 Best Practices for Feature Flagging:
  137. Feature toggles - A simple fix for complex release cycles:
  138. Feature Flags for True Continuous Deployment:
  139. The Complete Guide to Feature Flags:
  140. GitLab -- Learn more about Feature Flags - The next step in Progressive Delivery:
  141. CloudBees -- Evolving Continuous Delivery Using Feature Flags:
  142. Semaphore -- Feature Flags - A Gentle Introduction:
  143. Harness -- Feature Flags - What They Are & How To Use Them:
  144. Zero Downtime Database Changes with Feature Flags - Step by Step:
  145. How SREs Benefit From Feature Flags:
  146. 30 Feature Flagging Best Practices Mega Guide:
  147. Feature Flags: Make or Buy?: | SRC
  148. wikipedia: Code review
  149. PMD - Rules:
  150. The Secret to Code Quality in 2016 (INFOGRAPHICS): (hint: Code Reviews are key)
  151. Introducing JSLint plugin for Jenkins:
  152. WinLESS -- Online LESS compiler:
  153. Sassmeister -- Online SASS compiler:
  154. 'It's Not a Bug, It's a Feature.' (INABIAF) is it trite—or just right?':
  155. How to fix bugs that you can’t reproduce:
  156. History’s Most Expensive Software Bugs:
  157. Most expensive typo in history:
  158. Test Management and Bug Reporting:
  159. IBM Development solutions -- October 2008 - Minimizing code defects to improve software quality and lower development costs (WHITEPAPER):
  160. Fastly says single customer triggered bug behind mass internet outage:
  161. wikipedia: Bug tracking system
  162. jira-rest-tutorial-examples:
  163. JIRA REST API examples:
  164. Using Oauth Tokens with curl:
  165. python HTTP(S) requests -- how to disable / bypass proxy:
  166. Accelerating our journey to the cloud, together - Work Life by Atlassian:
  167. Link Bitbucket (Stash/On-Premise) with Jira (Cloud):
  168. What are issues in Jira?:
  169. JIRA Tutorial -- A Complete Guide for Beginners:
  170. Tutorial - Planning and Estimating work for an Agile team:
  171. Tutorial - Tracking a Kanban Team in JIRA:
  172. Learn scrum with JIRA Software:
  173. Fields Allowing Custom HTML or JavaScript:
  174. Configuring a custom field:
  175. Change your site logo and colors:
  176. Configuring time tracking: | TimeTracking (direct link)
  177. Configuring Estimation and Tracking:
  178. Remaining Estimate Time Tracking and Stories. How to Apply Time to Sub-Tasks during Planning:
  179. JIRA Upgrade guide to JIRA 4.2+ and how to enable Time Tracking feature:
  180. Time Tracking in JIRA:
  181. Advanced JQL searching:
  182. Work Logged Column:
  183. How can I generate a report of time logged per person and not per task?:
  184. JIRA -- find all my logged work for last week:
  185. JQL on work logged:
  186. JQL JIRA Filter on Worklog:
  187. Using watchers and @mentions effectively in JIRA:
  188. How do I associate an existing Kanban board to an existing JIRA project?: (ANSWER: 'you need to have project="Your Project" set somewhere in your JQL for it to show up as a "Board" under your Project, even after associating in Board Settings... so be sure to use an OR for the generic side of the JQL that filters on "Label" or "Component" from other projects)
  189. Issues are not appearing in Boards:
  190. How do I show completed items in the Done column of the Agile board?:
  191. 6 Tips Before and After Integrating Jira Software With Bitbucket
  192. Connect Bitbucket Cloud to JIRA Software Cloud:
  193. Release issues from The Kanban board:
  194. Using the release page to check the progress of a version:
  195. Automating JIRA Release Process:
  196. Best practice for creating a “Roadmap” in Jira [closed]:
  197. Product Roadmaps in JIRA:
  198. JIRA support -- SOLVED - "We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file":
  199. JIRA -- Configuring workflow triggers: (supported at least in v7.1+)
  200. How to write a JQL to find issues status changed on Last week?:
  201. How to find issues that at some point has been assigned to you?:
  202. JIRA -- Find all issues related to a user:
  203. How do I search for issues Resolved and/or Closed by a particular user? :
  204. How can I search issues to which a user has commented? :
  205. Find all JIRA issues I've ever commented:
  206. Issues commented by me in JIRA:
  207. How can I filter for all issues where I have commented?:
  208. Cloning an Issue:
  209. Integrating with development tools:
  210. JIRA -- Using parallel sprints:
  211. View stories in a closed Sprint:
  212. Two-level vs three-level story mapping with JIRA: (requires Marketplace plugin "StoryMapping by Stories OnBoard")
  213. Is this good acceptance criteria, in a JIRA?:
  214. Building "Definition of Done" and "Acceptance Criteria" lists in JIRA:
  215. How to handle a change in acceptance criteria for a user story?:
  216. 8 steps to a Definition of Done in JIRA:
  217. Scenarios for User Story in JIRA:
  218. Cucumber - Gherkin Keywords/Feature Introduction:
  219. Backbone Adds Native Support to Sync Data Across Jira Cloud Instances:
  220. How to find ID for custom field(s)?:
  221. Atlassian -- Create an admin API key: (for JIRA/BitBucket/Confluence cloud data)
  222. Atlassian -- JIRA/BitBucket - Manage API Tokens:
  223. JIRA API v2.0 - create issue:
  224. JIRA's v2.0 API example - listing for all Custom IDs:
  225. JIRA's v2.0 API example - "create issue" metadata:
  226. JIRA v3.0 API example - get Project versions:
  227. Jira API and SelectList with REST:
  228. How can I find the ID of a custom field in Jira 5?:
  229. JIRA's RESTful endpoint - getting worklogs: ((the proper path is /rest/api/2/issue/{issueIdOrKey}/worklog to get all worklogs of a given JIRA key))
  230. JQL example for searching for issues that have worklogs: project=CMSDEV AND Sprint in (15, 17) AND worklogDate >= 2018-01-17 AND worklogDate <= 2018-01-31
  231. Understanding the Cycle Time of Epics in Jira : (tip on setting a "Post Function" to move Epics to "In Progress" when they have child User Stories or other issues types that start their progress)
  232. How to administer a lot of projects in Jira:
  233. Can a company’s culture make or break agile adoption?:
  234. Spring Cleaning for JIRA:
  235. Chrome Extension -- JIRA Assistant:
  236. How to find issues added to active sprint in JIRA?:
  237. How can I filter issues not in active sprint (i.e. in backlog) for my dashboard?:
  238. What’s the difference between a Kanban board and a Scrum board? (in JIRA):
  239. Atlassian Training:
  240. Atlassian Incident Handbook:
  241. Atlassian launches Jira Ops, acquires OpsGenie for $295M:
  242. Atlassian acquires OpsGenie, launches Jira Ops for managing incidents:
  243. Atlassian to Acquire OpsGenie to Help IT Teams Manage Service Disruptions:
  244. Atlassian announces Jira Ops and intent to acquire OpsGenie:
  245. Next-gen projects -- the new project experience in Jira Software Cloud:
  246. "JIRA Roadmap" feature launched:
  247. Next-gen (actual JIRA team's) roadmap for Jira Software Cloud:
  248. Email Notifications:
  249. JIRA - Wiki Text Formatting Notation Help:
  250. Confluence Wiki Markup:
  251. Confluence Editing Improvements:
  252. Creating Issue Reports for Test Results: integration with testcomplete
  253. Introducing Jira Align!:
  254. What JIRA permissions are required to setup connection (to qTest)?:
  255. I want to be able to view closed issues in the new plan mode:
  256. How to enable HTML Email notifications?:
  257. Search for issues associated to inactive users: (using JQL assignee in inactiveUsers())
  258. Finding Issues Owned by Inactive Users with JQL:
  259. JQL "assignee was in membersOf() on" doesn't work like expected:
  260. What is used for? :
  261. Setting the assignee based on a property key:
  262. Microsoft Teams & JIRA:
  263. JQL to get the subtasks of specific issue:
  264. Is there a way to change a user's email address?:
  265. How to change users' email address? :
  266. Gartner Magic Quadrant -- Enterprise Agile Planning Tools:
  267. Confluence - Integration with Microsoft Streams:
  268. What is the new Jira issue view?:
  269. Two ways we’re simplifying how to create projects in Jira: (Classic=CompanyManaged, NextGen=TeamManaged... going forward)
  270. Jira templates for user stories, tasks and bugs:
  271. Atlassian -- Open DevOps solution:
  272. Atlassian blog -- Introducing "Open DevOps" - getting started:
  273. Atlassian reveals Open DevOps vision:
  274. PowerBI -- jira-powerbi-template:
  275. Microsoft Lists, a New Task Manager, Is Free if You’re Fast:
  276. Try Microsoft Lists with your Microsoft account (Preview):
  277. Microsoft Planner - task management:
  278. Five ticketing systems for developers:
  279. Benefits of the SDL:
  280. Systems Engineering for Intelligent Transportation Systems:
  281. Agile Software Development compliant to Safety Standards?:
  282. The Cost of Test Driven Development:
  283. What Does It Cost to Fix a Defect?:
  284. What Does It Cost You To Fix A Defect? And Why Should You Care?:
  285. The Rising Costs of Defects:
  286. Defect Prevention - Reducing Costs and Enhancing Quality:
  287. Lets Test 2012:
  288. The economics of Testing:
  289. How to Handle blocker bug in middle of Sprint:
  290. How to deal with bugs in Sprints:
  291. 4 Agile Ways to Handle Bugs in Production:
  292. Should defects have story points in Scrum?:
  293. How do you handle bugs during sprint planning?:
  294. How to manage bugs which open during active sprint w/o impact burndown:
  295. Best way to track bugs for stories?:
  296. How do you track bugs in your sprint?:
  297. How should a team handle Unplanned Work in Scrum (using Jira)?:
  298. How to track bugs during QA of a user story:
  299. Do you estimate bugs that are added before you add them to a sprint?:
  300. How to deal with Bugs in the Product Backlog & Sprints:
  301. We have over 450 bugs. Should I create a separate project just to handle bugs?:
  302. How do I create a Bug and have it appear as a Sub-Task under the related Story on the Agile Board?:

See Also

Build | GIT | SVN | CVS | Testing | PM | Agile | CI/CD | DevOps