Petru Simion [Simitech Ltd.] Atlassian Partner

@Fernando Eusebio Salazar Valencia You said you the field was "included to a screen and assigned to a scheme". This is ambiguous. To what screen did you included the field? Keep in mind that screens are associated with operations. Those operations are Create, Edit and View. So if you want to make a field editable, one step…

Hi @Lakshmi Kumari , You could try searching for every issue, the history tab. This can proove time consumming and error prone, since the Description field could be altered multiple times. If you are open to ussing apps, you can use Issue History Dashboard for Jira, an app released by our company.…

Hi @Muhammad Akram Sharifi While you could look at each and every ticket in the History tab and try to depict the value change on a field, this could prove time consumming and error prone. Especially that a field value could have been changed multiple times, on the same ticket. If you are open to apps you can use Issue…

@Ashima Bhatia When plugin are creating custom fields it deppends if/how the plugin marks that field as created by the plugin. Could be a comment in the field description. The plugin documentation should state that the plugin is creating custom fields and which they are. So the process will require you to analyse the…

@Zac Gouchie If you are open to using apps, you can use Issue History Dashboard for Jira, an app released by our company. https://marketplace.atlassian.com/apps/1235591/issue-history-dashboard-for-jira?hosting=cloud&tab=overview In the filter area, you can filter your searcy by Field Updated to be the field you…

@Gal Fatal , Determining how fields are used can prove a very time consuming operation. A field can be used in projects either as in one of the screens (create, edit, view) used in screen used in screen scheme -> issue type screen scheme -> associated to one or more projects or in workflows, where action screens(regardless…

@jodywhite While you can analyse each and every issue history to see if the issue was indeed added to the sprint (the updated value in the history is the Sprint field) and that happened after the sprint was started, this can be time consumming and can not be easily exported for further reporting and analysis. If you are…

You can use ScriptRunner and turn a text field into a list. See the ScriptRunner documentation.

Hi @Riyas Khareem , If you are open to using apps, you can use Issue History Dashboard for Jira, an app recently released by our company. https://marketplace.atlassian.com/apps/1235591/issue-history-dashboard-for-jira?hosting=cloud&tab=overview You can filter your search for Updated Field to be Sprint and the Date Updated…

@Riyas Khareem If you are open to using apps, you can use Issue History Dashboard for Jira, an app recently released by our company. You can filter your search for Updated Field to be Sprint and the Date Updated from and to to be your desired sprint start and end dates. The Value From and Value To columns are displaying…

Salut Danut, This confirms that a mechanism is required to specify the entry and exit calculation points. Does your app allow setting the entry and exit point of calculation for each issue type? Since each issue type can have it's own workflow... Thanks. Regads, Petru

I do understand the definitions. Lead time - duration from request made to delivery and Cycle Time - duration from work started to delivery. My question is not about that. It is about how can anyone know when the work starts and when delivery is made. This is going to be determined by how the customer defines it's…

Thank you @Bill Sheboy . I read some of the existing app documentation and articles, and found out the concepts I mentioned. I asked the question to determine if there are already established terms for Lead Time and Cycle Time that I might not be aware off. Regards, Petru

Hi @Dionne Hairsine , May I know what is your understanding/expectation of: * cycle time * average cycle time From what to what moment in time? Regards, Petru

@Loukia Balatsouka Users get into relationship with Projects through Roles. While Roles are specific to Projects, Users are defined globally and can be assigned to Roles in different Projects. If you need an overall view of roles across all projects in your organisation, you can try CIFJ - Roles Dashboard for Jira, an app…

@Rafael Garcia Tamarit JQL only returns issues. You can use CIFJ - Versions Dashboard for Jira, an app recently released by our company. https://marketplace.atlassian.com/apps/1235582/cifj-versions-dashboard-for-jira?hosting=cloud&tab=overview You can filter your search by projects, versions, start date from to, release…

@Vikrant Yadav If you are using cloud and you are open to use apps, you can use CIFJ - Issue History For Jira, an app recently released by our company. You can set the Updated Field = Status and Date Updated greater than your desired date. You can even add a certain value for the Value To in case you only want to filter…

If you are open to using apps, you can use CIFj - Issue History Dashboard for Jira, an app recently released by our company https://marketplace.atlassian.com/apps/1235591/cifj-issue-history-dashboard?hosting=cloud&tab=overview You can filter by Field Updated = Status and Change Date from and to as you need. If you need…

Hi @Dave Bair The Status filter field was changed to a simple text. You can now add manually the value of the Status name you intend to filter. Thanks for rising up this issue

Hi @Dave Bair The reason you are seing multiple roles with the same name is because they come probably from Team Managed Projects. We are going to implement a change in the app to deal with this. Will keep you updated.

Just do a first search for Project FORM and Field Updated = Status. Do you have any results?If yes, do you see any value "Rejected" in the column Updated To? About the fact that you have multiple statuses with the same name it looks weird. Statuses are global. They are used across projects. As an admin: Go to…

Hi @Richard Cieslik You can use CIFJ - Issue History for Jira Dashboard, an app recently released by our company. https://marketplace.atlassian.com/apps/1235591/cifj-issue-history-dashboard?hosting=cloud&tab=overview You can filter for those issues where the Field Updated has the value Status. You can also filter by Date…

Hi @Dave Bair I tested and the search works correctly. Please see attached img. * What I see is that you were able to add multiple statuses with label Rejected in your search field. That shouold not be possible, as Jira does not allow adding multiple statuses with the same label. The Status drop down field allows multiple…

Hi @Dave Bair I am looking into it. Will do a few tests and let you know. Glad you like the rest of the functionality. Regards, Petru

You can use CIFJ - Issue History Dashboard for Jira released by our company. https://marketplace.atlassian.com/apps/1235591/cifj-issue-history-dashboard?hosting=cloud&tab=overview You can export the search result to CSV, open in Excel then use Excel capabilities to find the differences. Method 1: Conditional Formatting 1.…

You can use the app recently released by our company CIFJ - Issue History for Jira https://marketplace.atlassian.com/apps/1235591/cifj-issue-history-dashboard?hosting=cloud&tab=overview You can search, filter by issue change date to be between the dates you mentioned and you will get the list of issues matching your search…

You can use CIFJ - Issue History For Jira https://marketplace.atlassian.com/apps/1235591/cifj-issue-history-dashboard? hosting=cloud&tab=overview The app is recently released by our company. You can search and filter issue history using the field Updated By. Once you obtained your desired result you can either use the list…

Checking issue by issue in History can proove inneficient. You can use CIFJ - Issue History Dashboard for Jira, an app developed by our company. https://marketplace.atlassian.com/apps/1235591/cifj-issue-history-dashboard?hosting=cloud&tab=overview You can search, filter and export to CSV for isssue history in any project.

In order to know what to bulk change you need to analyze the changes. https://marketplace.atlassian.com/apps/1235591/cifj-issue-history-dashboard?hosting=cloud&tab=overview CIFJ - Issue History Dashboard for Jira, an app that our company just released, can help you search, filter and export to CSV such data. You can later…

You can use the app developed by our company, CIFJ - Issue History Dashboard for Jira https://marketplace.atlassian.com/apps/1235591/cifj-issue-history-dashboard?hosting=cloud&tab=overview You can search, filter and export issue history changes by project.