Ignacio Pulgar Expert

https://jira.atlassian.com/browse/JRA-63300

I would suggest creating either a kanban or a scrum board for managing multiple projects. The board's query may be something like: project in (A, B, C, D) ORDER BY Rank ASC where letters A to D represent the keys or names of the projects you would like to be able to manage from a single view. You may create 4 board's Quick…

No that I know, but you can request Atlassian Support to restore the last backup on a temporary JIRA instance. They will need the date and hour when this accident happened in order to get the last copy before the data loss.

I agree with Robert's answer (+1'ed!). Provided that a symptom may be produced by different root causes, I'd say it would be better not to assume that it is the very same bug, before having researched on it: What would it happen if, after having reopened the old issue and worked on it for several days, you notice that it…

What exact action are you performing and when is that error being shown?

Thank you, Jobin.

I've also experienced a similar issue, but the columns can always finally been configured after several tries, reloading the page and trying again. I'm not sure if it might have anything to do with the browser's cache...

Just in case you need it for keeping your projects organized, you can create project categories through the UI instead.

I think the only available workaround is: * Add the 'important' label to all issues linked with a so labelled epic. For doing that, execute your query: "Epic Link" in (list_of_epics) Click on the button Tools on the top-right corner > all X issues Select all issues > Next Edit issues > Next Click 'Change Labels' > Add to…

status CHANGED TO Closed AFTER "2014/11/01" AND status = Closed

That JQL returns all issues where you have ever been the assignee since its creation date (including those in which you are the current assignee), but only if it has been updated after the start of the previous day. Note that the issue is considered to be updated when the assignee changes, but also when a new comment has…

+1

Try this: assignee WAS currentUser() and updated > startOfDay(-1) It is not exactly what you said, but will certainly help you.

I'm afraid that Time Tracking fields cannot currently be shown in the customer portal.

Do you mean that you would like SLA timers to be viewable by customers through the customer portal?

If you are looking for the monthly payment plan, you may choose between: * up to 3 Service Desk agents tier + up to 10 JIRA Software users tier = $20 USD / month (customer accounts are free on this option) (you may optionally add Confluence for 10 users for $10 extra per month, which I'd recommend) * up to 50 JIRA Software…

If all projects are for software development, you will need 39 JIRA Software user licenses. If some projects are for maintenance (incident management, subject to SLAs you are supposed to be able to report on...) then you will need Service Desk (lowest tier), and customers who only need access to the Service Desk customer…

By becoming an Atlassian Expert your organization will have to perform some tasks of a so-called onboarding program. On of those tasks consists of building a local instance of JIRA (among other Atlassian products) for a fictitious enterprise called Teams In Space. While that local deployment was designed for demo purposes,…

* Both. Atlassian backups every instance on a daily basis, but just for recovery against critical incidents. They aren't contractually enforced to use it so that you can recover a set of issues accidentally deleted, or something the like. You can also create your own backups, which could let you reset your instance to a…

You need to add the Resolve Issue Screen in a workflow transition (arrow) that goes to the final status (Resolved or Closed...). Then, you will be promted a dialog to set the Resolution on changing to that status.

Could you paste here the Work On Issues permission set on the project? (find it in the permission scheme used by your project) Maybe, the permission scheme grants Work On Issues permission based on an issue role, like being the Assignee.

"Resolved Date" seems to be a custom field, possibly created manually. The field used by JIRA is displayed as "Resolved" in the column header. Just remove the "Resolved Date" column and include "Resolved".

De nada 

Hola Marta, Ok, ya entiendo. Hay algunas formas de obtener esa 'foto' del estado del proyecto, aunque requieren haberlas planificado con antelación. Es decir, desde el momento actual no sería posible obtener fotos del pasado, a menos que se hubieran tomado en ese momento. Es decir, para conservar la información acerca de…

Hola Marta, ¿Podrías poner un ejemplo de lo que te gustaría conseguir? Y ¿tienes JIRA Software, o sólo JIRA Core? Si tienes JIRA Software, ¿es esa la clase de proyecto en la que lo deseas conseguir? ¿Estás familiarizada con Scrum? Saludos

Please, find here the documentation about workflows: https://confluence.atlassian.com/adminjiracloud/issue-workflows-844500760.html

The 'split' option is available from a board's backlog, by clicking on an issue with the mouse's right button: split.jpg

Volodymyr's answer is correct, although it requires coding skills and time. Alternatively, you can buy a cheap addon for getting what you need. I use and recommend Time Reports: * Good support * Continual improvements * Cheap Hope it helps.

The backlog let's you combine both Quick Filters with Epics: epic-tasks.jpg

You may configure your board's Quick Filters queries like: * type = epic * type = task * type = subtask quick-filter.jpg And apply that filter to the issues displayed in your board with one click: tasks.jpg