It can be set when they review the “notes” field, or automation can be applied to calculate it directly as a function of the workflow status. The project manager can handle this field manually.It’s like the field “Status name to show customer” in Jira Service Management.Customer status: This field communicates the status of the issue from the customer’s perspective.For example: “Information provided to your purchase team (David Nusbaum, email ), and waiting feedback,” or “Currently in internal testing, expecting to install on UAT environment around the end of October.” The language and level of detail should be relevant for the customer, highlighting specific information requiring their attention.Ideally, the project manager reviews this field weekly and updates it to reflect the current state of the issue.The team knows that they should not use or modify this field.Notes: This field is solely used by the project manager.Customer project: When issues related to several customer projects are managed in a single Jira project, this field associates the issue with the customer project.This configuration is extended with custom fields, which create the foundation for sharing information with the customer. It is your internal kitchen, and there aren’t any client “chefs” allowed. This is the key point: the customer does not have access to Jira. ![]() Even the split of issues to different projects should follow your internal organizational structure and is not dictated by a specific customer project. The sprints rhythm, the Kanban board columns, and the custom fields and permissions follow a common framework. The Jira instance is used for all different projects and is your team’s main playground. Jira is where your internal development work happens. What’s Jira’s role in this setup, and what needs to be configured? There is no need for support from system admins, nor is there any dependency on sophisticated synchronization apps with complicated setups. The setup is easy, and it’s mainly under the project manager’s control.There is no double bookkeeping - the system is the solitary source of truth.The customer gets a satisfying view of the project’s progress and is clear when the development team needs their input.The internal team has full autonomy: They use Jira openly without worrying about how things might look from the customers’ perspective, free to discuss the sticky bits, previous projects, and concerns.The setup I’m sharing checks all the essential boxes for an optimized system and has the following benefits: How to use Jira and Confluence for project collaborationĪ combination of Jira and Confluence is the perfect solution for project managers to help both clients and developers perform at their best. Once data is ready in Jira, we’ll leverage Jira Snapshots to achieve export epiphany. Let’s see how to configure Jira to streamline client reporting- so that you have the data you want to share when you need it. Our own Confluence App streamlines Jira data exports and solves the hurdles of exporting Jira data to file. Meet Jira Snapshots – Time-Stamped Exports Into Confluence. There should be a better way to export data from Jira and share it with clients. For example, if I want to export all the project tasks and their subtasks, it’s impossible to do this kind of export straight from the platform. Third, exporting from Jira does not provide for a multi-level option. ![]() A problem because redlining different versions of the report is one of those things that careful budget owners like to do. This method does not lend itself to good redlining of the data coming from Jira. You need to convert the data into an editable format- import your CSV to a WORD doc and then add the rest of the text. There is a lot of background information that you want to add to any report. Second, the Jira data is only part of what you want to share with the customer. To be honest, this becomes double bookkeeping for the project. So this means you need to put it wherever you put all the project documentation, decide on a filing and tagging method, and keep this consistently. First, there is a question of how to share this file- email is difficult to trace and manage as a long-term collaboration tool. ![]() The exported file gives a sense of control – you control which issues are shared and what fields are included.īut, exporting to a file is not without its problems. Hence it has become common to export Jira data and share the exported static copy with customers and other 3rd parties. It’s like bringing guests into your kitchen, where they might catch a glimpse of dirty dishes. Most project managers rather not give clients direct access to Jira. Developers want to protect their autonomy, while clients want to be kept in the loop. Project managers are often pulled in two separate directions by the people they serve: their team and clients.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |