![]() ![]() customerRequest ( CustomerRequest): The current customer request.serviceDesk ( ServiceDesk): The current service desk.project ( Project): The current project.Requests made by Forge apps must be authenticated with asApp().Īvailable when a JQL query is specified in the request context when using the REST API. Or Forge app that made the request or provided the module.Īlways available for expressions used in app modules and REST API requests made by apps. Equal to null if the request is anonymous. Indexed accessįor example, to get the first issue comment, write:ĭepending on the context in which a Jira expression is evaluated, different context variables may be available: The operator can also be used in combination with computed member access, for example: issue?. issue?.customfield_10010-this expression returns null if the custom field doesn't exist.Or if there is no a.b path in the value of the property. issue.properties?.myProperty?.a?.b-this expression returns null if there is no myProperty defined in the issue,.When accessing the property fails, null is returned. This operator behaves in the same way as regular member access, but with one crucial difference: In expressions where such strict rules are not desired, use the optional chaining operator ?. For example, in the expression a.b where the value of a is null. the left-hand side of the operation is null.See all the Requirements Management apps in Atlassian Marketplace.2 issue.propertiesĪccessing properties in a Jira expression may fail, for example, where: RMsis - A Requirement Management Extension for JIRA.Prefer to customize your Atlassian products? The Atlassian Marketplace has dozens of Requirements Management apps which can easily be tailored to your workflow. To facilitate documenting your requirements, Confluence ships with a Blueprint template for requirements writing: Product Requirements Blueprint. Using ConfluenceĬonfluence integrates seamlessly with JIRA, allowing you to track your requirements in JIRA, linked to your corresponding project documentation in Confluence. Sub-tasks offer a quick way to add and manage your requirements, and you can link related requirements together or with feature requests. ![]() You're able to create a JIRA issue type specifically for requirements with its own workflow, custom fields and reporting. ![]() The wiki allows our developers to edit the requirements as needed while making it easy for developers and stakeholders to stay up to speed. We then utilize Confluence and JIRA's integration to create issues from those requirements pages allowing us to view both the requirements content in line with the JIRA issues/tasks which correspond to the project. Atlassian's UsageĪtlassian uses a public instance for our requirements management through feature requests and voting on our public issue tracker.įor internal discussion, we use Confluence for general requirements gathering and project discussion on a Confluence page. We will review how Atlassian uses our products for this purpose, as well as provide some relevant resources for further information. While JIRA has been developed primarily as an issue and project tracker out of the box, you can use JIRA for requirements management in conjunction with Confluence. This article only applies to Atlassian products on the server and data center platforms. Platform notice: Server and Data Center only. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |