Böcker av Matthew B. Doar

If you're familiar with JIRA for issue tracking, bug tracking, and other uses, you know it can sometimes be tricky to set up and manage. In this concise book, software toolsmith Matt Doar clarifies some of the more confusing aspects by answering difficult and frequently asked questions about JIRA administration.Practical JIRA Administration shows you how JIRA is intended to be used, making it an ideal supplement to the extensive documentation already available. The books chapters are loosely connected, so you can go straight to the information that best serves your needs.Understand the difference between JIRA groups and JIRA project rolesDiscover what JIRA schemes do, and learn how to maintain themUse a consistent configuration approach to help you use JIRA as a platformCreate a workflow from scratchAdd, modify, and deactivate usersPrepare for a JIRA upgrade, and troubleshoot if necessaryGet remote access to JIRA via email, SQL, REST, and other methods

One advantage of using JIRA for issue tracking, bug tracking, or project management is the ability to extend this tool with hundreds of plugins from the JIRA community. In this concise book, software toolsmith Matt Doarthe author of Practical JIRA Administrationshows you how to create and maintain your own JIRA plugins to meet the specific needs of a project.This book uses detailed examples to clarify some of the more confusing aspects of JIRA plugins, and serves as an ideal supplement to the extensive documentation already available.Use JIRAs Plugin SDK, and learn several aspects common to all pluginsCreate your own custom field type, using a JIRA pluginDelve into advanced aspects of custom field plugins, and discover how searching for values in custom fields worksCreate JIRA plugins to use with workflows, and learn about conditions, validators, and post-functionsStore data using the PropertySet interface and the Active Objects pluginUpgrade a plugin and upload it to Atlassian Plugin Exchange (PAC)

This book doesn't tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus some more things you'll wish you had known before starting a project.Practical Development Environments is a guide, a collection of advice about real development environments for small to medium-sized projects and groups. Each of the chapters considers a different kind of tool - tools for tracking versions of files, build tools, testing tools, bug-tracking tools, tools for creating documentation, and tools for creating packaged releases. Each chapter discusses what you should look for in that kind of tool and what to avoid, and also describes some good ideas, bad ideas, and annoying experiences for each area. Specific instances of each type of tool are described in enough detail so that you can decide which ones you want to investigate further.Developers want to write code, not maintain makefiles. Writers want to write content instead of manage templates. IT provides machines, but doesn't have time to maintain all the different tools. Managers want the product to move smoothly from development to release, and are interested in tools to help this happen more often. Whether as a full-time position or just because they are helpful, all projects have toolsmiths: making choices about tools, installing them, and then maintaining the tools that everyone else depends upon. This book is especially for everyone who ends up being a toolsmith for his or her group.