Petru Simion [Simitech Ltd.] Atlassian Partner

Hi @Naresh Rajak , An automated solution using custom fields will only work from the moment the solution has been implemented, leaving you with your other issues uncalculated. The issue history tab will reveal the first time the issue was transitioned into status In Progress as well as the date. One can calculate the…

HI @Natalie Keane , You will need to get familiar with how fields are related to projects starting with the diagram I just posted. The diagram explains clearly the way fields are related to projects: * field -> screen -> screen scheme -> issue type screen scheme -> project * field -> screen -> workflow action -> workflow…

@Evert Morren Atlas Admin , This is possible with a custom solution, not of the shelf. You can create an issue type that will serve such transformations. The issue type will have an action button, that does not need to transition the issue, just allow for an action to happen. You will add a condition restricting this…

Just realized the solution is already provided.

Hi @Lawrence Rawlins , Status is not an attribute that is changed like the value of a field. Statuses are labels that are mapped to steps in workflows. For simplicity usually the workflow step and the status have the same value such in To Do -> In Progress -> Done. But keep in mind that the status and workflow step label…

Hi @Eric Lynch , Boards are views into the data. Each column can be mapped to one or more workflow statuses. Every company designs it's workflows potentially differently, even if some are probably similar when dealing with established processes. However Jira allows this complex mapping of statuses to columns, coming from…

Hi @Philip Abdalla , The information is available in issue history, and the JIRA REST API allows you to extract all that information, however it will prove code intensive and will take a significant time to develop and test. Using a custom field to record the last change, aka blockage has two caveats. One is that the…

Hi @Dorothy De Pina , While the REST API allows you to get the history activity for issues, the returned format is JSON and would probably require extracting the essential data you need. If you are open to using apps you can use Issue History Dashboard for Jira , an app released by our company. You can search for either…

Hi @anna_charles , This can happen if: 1. The field configuration associated with the Story and Epic for the project(s) is made required. 2. If your company is using Behaviours, a specific behaviour was added to make the field required. For both these you need to ask a jira admin, that has access to the configurations and…

Hi @Harry Coleman To understand how fields are displayed in issues across projects, you need to grasp the following relationships: 1. Fields are placed on Screens. 2. Screens are added to Screen Schemes. 3. Issue Type Screen Schemes map each Issue Type to a Screen Scheme. 4. Issue Type Screen Schemes are used in one or…

HI @Natalie Keane , When working with fields in Jira, it's essential to understand their relationships and configurations. Fields can be used by projects in two ways: 1. Through create, edit, or view screens 2. As part of transition screens in workflows used by the project The diagram below illustrates these relationships.…

Hi @Dhruti Shah , Jira's flexibility allows anyone to define custom workflows tailored to their unique processes. However, this flexibility presents a challenge when calculating process duration or segment timelines. Since each process can have multiple workflow steps associated with various statuses, determining entry and…

Hi @Brian Donaghy The following is about company managed projects. When a field context is not global and is restricted to specific projects and issue types, it's crucial to coordinate its usage logically. This involves understanding: - Which screens (create, edit, and view) are used in each project - Which transition…

@Yves Defossez , To determine the exact time an issue spent in a specific status, you'll need to analyze the issue history and manually calculate the duration. This involves: - Identifying the timestamp when the issue transitioned into the specified status - Identifying the timestamp when the issue moved out of that status…

Hi @Marty Monaco, Creating an automation rule to populate a custom field is possible, but please note that it will only take effect moving forward, from the moment the rule is established. Existing issues will not be retroactively updated. Saving the value in custom fields is also a problem when you want to analyse the…

Hi @Khai Ha , To track time spent in a status, particularly when an issue is moved in and out of that status multiple times, you can create custom fields to record this data. However, this solution has a significant caveat: it will only work from the moment it's implemented, leaving existing issues without calculated data.…

No.

HI @Aylin Tüzün Yücel , Determining how much time your issues are spending in a project is related to what your company vision is as time spend in a project and the way your workflows are defined. For example, do you want to track the time that the issue spent in active statuses, such as In Progress? Or do you want to add…

Hi @Patrick Wright , A Jira Project of type Software supports Sprints, and therefore the notion of a Backlog. When an issue is created for such a project it appears in the Backlog. This is because, conceptually, the issue is a candidate to be dealt with in a future Sprint. If you want your team to have different views into…

HI @wvacchiani , When issued are moved between projects the issue history for each issue is registering two changes. One is that of the project and the second is for the issue key. While going through each issue and observing this change in history is possible, it can be time consumming and error prone. If you are open to…

Hi @Lacy Saute , Roles are project specific. This makes it challenging to visualize the overal role usage across all projects in your organisation, and can result in confusion when the same role name is used in multiple projects but in different ways and with different users or groups associated. If you are open to using…

Hi @Rajkumar Rajamanickam If you are open to using apps you can use Issue History Dashboard for Jira , an app released by our company. As per the attached img, you can filter to search for only specific values for fields. It does not matter if you search for system or custom fields, it works the same. In this example the…

Hi @Elvis , Deppending on what your company considers a re-opened ticket, it would mean transitioning the ticket back into a specific status. Probably the first status in the workflow regardless of how it is named: To Do, Open etc. You could search each issue history and try to see if the ticket was transitioned back into…

Hi @gordon.varney , If you are open to using apps you can use Issue History Dashboard for Jira an app released by our company. You can filter to only search for history change items that are about changing the issue type by using the filter field "Field Updated", select the Issue Type value. You will be able to see what…

Hi @shay ron , You can only visualise the change timestamp for the status in each issue history. In order to visualize and export multiple issues, and potentially multiple status changes within each issue, you can use Issue History Dashboard for Jira an app released by our company. You can sort your filtered search to only…

Hi @Nissim Ariel , For each field you want to use in a project you will: * Add the field to a screen* Screens can be associated with operations: Create, Edit View * Add the screen to a Screen Scheme * Associate the Screen Scheme to an Issue Type. This is done in an Issue Type Screen Scheme * Associate the Issue Type Screen…

@Max Each project allows, throught the permission scheme, setting who can do what in that project. A permission scheme can either assign permissions to individual users, group of users or roles. Roles are defined within each project and each role can contain either individual users or groups. While this configuration is…

@Tim Williams As already mentioned, the History tab will allow you to depict the changes you are looking for, issue by issue. If you deal with a large number of issues, this might proove tedious and error prone. If you are oppen to using apps, you can try Issue History Dashboard for Jira, an app released by our company.…

Hi @John Morrow , While using roles in a project is more or less straight forward, envisioning this over an entire enterprise can be challenging. Roles can be associated directly with users, or indirectly with users, via groups that users are part of. If you are open to using apps, you can use Roles Dashboard for Jira, an…

Hi @Ratom , Using fields requires coordinating multiple factors. One is the field confguration, that specifies how the field is used by projects and issue types within those projects. However that does not make the field visible or applicable unless you use it. If you use it in screens associated with Create, Edit or View…