Petru Simion [Simitech Ltd.] Atlassian Partner

Hi @Sherwin Soriano , If you are open to using apps you can use Issue History Dashboard for Jira (Work Item History) , an app released by our company. You can search by Field Updated = Sprint and you can see how the value was changed in columns Value From, Value To. Regards, Petru

Hi @Muammad Faizan Iftikhar , You can write a scripted field that will parse automatically the issue history and display all the historic values the way you chose. The advantage is that it will work with existing data as well as new data. Other solutions, such as capturing the values in another field, every time the field…

Hi @Édpo César , You can create a scripted field that parses the issue history and calculates the diffs. Alternativelly, if you are open to using apps, you can use Issue History Dashboard for Jira (Work Item History) , an app released by our company. You can filter by Field Updated = [Your field] then order the columns by…

Hi @Katarzyna Turnau , Roles are defined in projects, and each role in the project can be used in different ways, depending on your project permission scheme as well as the way they are used in your workflows conditions, validators and post functions. If your organisation needs a comprehensive approach over how roles are…

Hi @Gaurav Chandra Tiwari If you are open to using apps you can use Issue History Dashboard for Jira (Work Item History) an app delivered by our company. You can filter your search by: Updted By - yourself, Field Updated - Status, Value To - The value of your first step in the workflow. The result is exportable to CSV.…

Hi pvala@micron.com , If you are open to using apps you can use Issue History Dashboard for Jira (Work Item History) , an app released by our company. You can filter by Creation Date from and to and Date of Change from to and export your result to CSV. Regards, Petru

Hi @Charles Brooks , If you are open to using apps you can use Issue History Dashboard for Jira (Work Item History) an app released by our company. You can search all issues history by project, or if you need to filter out there are multiple filtering criteria. The result is presented in a sortable table that is exportable…

Hi @Mohith Tummala , You can write a scripted field that will search the history of the ticket and display the information you need. A scripted field will act on existing and new created tickets. If you are open to using apps you can use Issue History Dashboard for Jira (Work Item History) an app released by our company.…

Hi @thumuluru.shreya , If you are open to using apps you can use Issue History Dashboard for Jira (Work Item History) an app released by our company. You can search history by project or filter out by various criteria and export your ile in CSV format. Regards, Petru

Hi @Pedro Webster , If you are open to using apps you can use Issue History Dashboard for Jira (Work Items) an app provided by our company. You can filter your search by Field Updated to be the field that you consider the flag. Result is exportable to CSV. Regards, Petru

Hi @Shaun McGuire , If you are open to using apps you can use Time in Status Dashboard for Jira an app released by our company. You can search time in status for issues by project, or narrow down your search by filtering. Your result will be displayed in two perspectives. Columns Rows Result is exportable in CSV format for…

Hi @Moheb Hedayat , Deppending what reports you need to be creating, if you are open to using apps, you cn use one of these apps released by our company. Some of these apps will allow you to create reports about your configurations across your organisation and some about the data (issues) * Issue History Dashboard for…

Hi @Saad Ahmad , If you are open to using apps you can use one of the following apps, provided by our company. * Issue History Dashboard for Jira Filter by Field Updated "Status" and the Date of Change from and to according to your needs. Columns Value from and Value To are displaying the status from which was To Do and…

I found the solution myself it is using object NOT having inR(objectType = "[OBJECT TYPE]")

Hi @Uwe Pilz , You will need to write a script that will call the API function repeteadly untill you extract all values. If you are open to using apps you can use Issue History Dashboard for Jira an app provided by our company. You can retreive all values of history for all issues by project, or you can filter by various…

Hi @maggie.pople , If you are open to using apps you can use Issue History Dashboard for Jira an app provided by our company. You can filter by field Updated By and obtain your result in a sortable paginated table If you need you can export the search result in CSV format for further analysis. Regards, Petru

Hi @joel.geller , You can not achieve this with of the shelf Jira features. If you are open to using apps you can use Issue History Dashboard for Jira an app provided by our company. You can filter by Field Updated - Due Date. You can export your result in csv format for further analysis. Regards, Petru

Hi @Sam Tang , You can write your own script to extract this date. There is no functionality of the shelf in Jira that will provide you this. If you are open to using apps you can use Issue History Dashboard for Jira an app provided by our company. You can filter by Assignee then order your columns as you wish. You can…

Hi @Sanam Malleswari , I would not advise to use any app to automatically remove users from permission schemes, remove users from grouips or delete users. You could easily end up with a regretable mess. You need to do your analysis and manually remove users or alter your permission schemes, not before backing up your…

Hi @xin_wang , Envisioning how Permission schemes work, witout an enterprise view on roles and groups is challenging. The solution in an enterprise is requiring collaboration between the Jira admin who creates the groups and assigns users to group, creates roles and creates permission schemes, that are using roles and/or…

@Ramchandra Kudtarkar Stating that this is "expected behaviour" not correct. Expected behavior is that when the impersonator impersonates a user, the impersonator will act 100% like the user in all aspects. Any deviation is not allowing the impersonator to have the same experience as the impersonated. As a result the…

I have the same issue but I noticed the problem manifests only if when I was impersonating a user. When the user logged in directly the problem did not manifest.

New findings. The problem only manifests when, as a site admin, I loged in as another user. I created a test user account. When I log in as that user all works fine. When I log in as an admin(developer) and I use the Log in as user feature, and I impersonate the same user the user does not have access to resources error…

The problem manifests on two different sites (Work and Personal). They have total different DNS so this could not be the issue.

When creating the Hello World app using forge create, the resulting manifest file does not contain any scopes. If these scopes would be required the generated manifest should contain the correct scopes for the app to work. Tried with a few scopes like read:jira-work and read:issue-details:jira but same result. Bottom line…

The problem is that we have developed an app, based of the template. All works fine, and the final tests revealed the problem. In order to eliminate any issue we could have created, we tested with a simple Hello World app. Same problem.

I did not even use tunneling. Just deployed and installed. Works for the developer. Not for any other user.

No needs to appoligise :-) I added the details after your reponse. I just used the forge create, followed by selecting Jira and issue panel. The issue panel displays first Loading, which comes from the frontend file. The invoke function calls the backend, which returns a "Hello world " string that replaces the Loading.…

We deployed to production, same problem. We also tried to share the app and deploy vial shared link, same problem.

We have the same problem. In order to eliminate any issues created by our code we tested a simple Hello World application created by using the forge create command. Same issue manifests. If the developer executes it it works fine. The issue panel shows first message Loading, then the backend returns a string and this…