Ignacio Pulgar Expert

Requires the help of an addon, ie ScriptRunner: type=Task AND status!=Done OR (issueFunction in subtasksOf("status!=Done"))

A csv import will update existing issues if a column with issue keys is mapped to issuekey field. Including the summary is also required, even if you are just updating instead of creating new issues. Ensure all columns contain valid data for the fields you are going to map them to. By following the import wizard till the…

I tried that approach with Postman only.

Oh, I see! Thanks for the update!

Create an API token and replace your password with it: https://confluence.atlassian.com/cloud/api-tokens-938839638.html

Hi Hector, Not really, provided that none of these numbers would actually decrease by using that method: * # Custom fields * # Issues * # Configuration Schemes A slight reindex performance improvement might be experienced in case you remove archived projects from custom field contexts, but it would hardly be noticeable.

Hi Tarkan, Did you finally raise a ticket with Atlassian Support? https://support.atlassian.com/contact Regards.

After reading your question a second time and having tested a bit, my initial answer has no relationship with it. Sorry for that. Please, double check with the Permission Helper that people count with the permissions you mentiomed and Browse Projects. If they have all permissions, open a ticket to Atlassian Support.

If you get results on removing just "Status = Closed" from that JQL, it means that the resolution field is being set in a previous status, ie: Resolved. The query is ok, but the resolution date is not the same date when the issue moved to the Closed status. You may want to change your JQL by substituting the references to…

There have been some changes in order to improve privacy and to better algn with GDPR. "As part of an effort to consolidate user profiles, we're phasing out usernames in favor of using full names and public names when users are searched for and referenced in Jira Cloud and Bitbucket Cloud." Apps that you or your users may…

Maybe the date format in the csv does not match the date format indicated during the import wizard from csv. https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html More info about date formats: http://docs.oracle.com/javase/6/docs/api/java/text/SimpleDateFormat.html Hope it helps.

A popular choice for that purpose is Questions for Confluence: https://marketplace.atlassian.com/apps/1211644/questions-for-confluence?hosting=cloud&tab=overview That was the software which fueled Atlassian Answers, the predecesor of this Atlassian Community. Hope it helps.

Hi Keros, A way for doing so would be like this: * Save a filter with the following JQL: "Satisfaction date" >= -15m AND Satisfaction < 3 * Subscribe to that filter every 15 minutes. Having set that, you'll be notified every 15 minutes of the new satisfaction scores lower than 3, rated in the last 15 minutes. Hope it helps.

Hi Dean, You may add custom comments for each status change by using a custom automation rule like, if I remember correctly: WHEN status changed IF status = "In Progress" THEN add a public comment: "The team has started working on this ticket" ELSE IF status = Done THEN add a public comment... And so on. Hope it helps.

That field type requires to count with an asset management addon. Note that Insight for Jira Cloud is free for the moment, although it is also in beta phase. Automatic issue linking would require custom scripting, ie through the help of ScriptRunner.

What do you need the customers to be able to do exactly? What would that user field be used for? The customers capabilities are limited by their free license type.

For that purpose, usually a Service Desk Agent creates a request on behalf of a customer by setting the Reporter field with the appropriate Service Desk Customer. Note that it requires Modify Reporter permission. Hope it helps.

Hi Adeel, Two important questions here: * Server or Cloud? * Does the instance count with ScriptRunner? Without the help of a third party app, like SR, you may get the info you need by exporting issues to CSV and treat the resulting spreadsheet as per your needs. The query #7 is the only one that can be obtained through a…

Besides that, there's a method for generating custom field values through a csv import: https://confluence.atlassian.com/jirakb/how-to-bulk-import-custom-field-values-for-certain-types-of-custom-field-827123935.html

While the list of values were the same, you may use the field in multiple pojects. If the list of options changes for some projects, configure a different context for each one, using just one custom field, instead of multiple fields, whenever possible.…

These are my two cents: * Use a scrum board. It counts with more builtin reports than a kanban board, which would let others track your progress. * Describe issues as if a different person were responsible for resolving them. * Use standard naming conventions for versions and sprint names. Sprint names should include the…

I'm afraid there's no way to achieve that with permissions, or any other method that I know. The most similar thing you may achieve would be manually controlling moments in which the people who should have limited permissions have, or don't have the Schedule Issue permission. The process would be: * Set the Schedule Issues…

Hi Rodrigo, If I'm understanding it correctly, you cannot edit the issue type. If that's the case, that usually means that the original and destination issue types use different workflows, and that a ...>Move action is needed for changing the issue type, instead of a simple edit. The move action is a little bit…

Oh, I see. Then Aron's approach would answer this question much better than mine 😊

Hi Sondra, When sharing a search, users clicking on the link will execute the search according to their own permissions to actually see the results. Therefore, unless all users have the same permissions in all scoped projects, they will probably see different results on executing the search. That's the expected behaviour.…

Hi Kiran, That's doable by subscribing to a saved filter with the columns (fields) you want to be emailed: https://confluence.atlassian.com/jiracoreserver0713/working-with-search-results-964984590.html Look at the subscription section. Hope it helps.

Hi Arun, Natively, the most "dimensional" feature you can use for reporting would be: 1. Create and save a filter named Defects with this JQL: type = Defect 2. Add the Two Dimensional Gadget to a dashboard you own. 3. Set the Defects filter to feed the gadget, and set a couple of fields you would like to get insight from…

Hi Erik, Ranking backlog issues requires Edit Issues & Schedule Issues permission. So, yes, users you remove schedule issues permission would become unable to prioritize issues in the backlog. Regards

Hi Kirill, Try this: 1. Create and save a filter like this one: text ~ reuters OR text ~ exegy OR text ~ mbpipe OR text ~ bpipe 2. Add the Issue Statistics gadget to a board, set to be based on Project, and fed by the newly created filter. Repeat both steps for each term, changing the filter accordingly in order to have…

I've looked the Atlassian Market for version related apps, but have not found one which provides the feature of creating new fields at the version level: https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=Version Some of them have other interesting features, though. As a workaround, would it be…