Over the top OCD: A master product requirement document, with subpages interconnected with Jira issues so that you can track progress.Mid level OCD: Build the requirements structure in Jira and flush out the details of the requirements on Confluence pages.Low level OCD: Put the entire specification in one Confluence document.Using the deadly duo of Confluence and Jira (Atlasssian’s issue tracker), your have multiple options for documenting product requirements depending on your degree of obsessive compulsiveness*: Mapping out the process user follow within Confluence.Selecting the Confluence documentation to use, so we will look at product requirement documentation options available within the platfrom.Doing this gives you control over when to propagate Quick Start updates to your deployment.So now that you have your space set up, the next step is building out a requirement gathering workflow, which consists of two main parts: This could introduce unexpected (and possibly breaking) changes to your deployment.įor production environments, we recommend that you copy the Quick Start templates into your own S3 bucket. These updates sometimes involve adding or removing parameters from the templates. However, when you do, any updates we make to the Quick Start templates will propagate directly to your deployment. The fastest way to launch the Quick Start is directly from its AWS S3 bucket. Launching the Quick Start from your own S3 bucket (recommended) For detailed instructions on how to do this, see Use the jira-config.properties file to customize an AWS Quick Start deployment. You can also use the same file to apply the same settings to an existing Quick Start deployment. Jira Server allows you to apply advanced settings through the jira-config.properties file. Amazon CloudWatch : Basic monitoring and centralized logging through Amazon's native CloudWatch service.įor more information, see Jira products on AWS.Database: Your choice of shared database instance – Amazon RDS or Amazon Aurora.The Quick Start architecture implements the shared file system using the highly available Amazon Elastic File System (Amazon EFS) service. Amazon EFS: A shared file system for storing artifacts in a common location, accessible to multiple Jira nodes.Load balancer: An Application Load Balancer (ALB), which works both as load balancer and SSL-terminating reverse proxy.Instances/nodes: One or more Amazon Elastic Cloud (EC2) instances as cluster nodes, running Jira.The deployment consists of the following components: Here's an overview of the architecture for the Jira Data Center Quick Start: For more information, see Atlassian Standard Infrastructure (ASI) on AWS. The ASI is a virtual private cloud (VPC) that contains the components required by all Atlassian Data Center applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |