Phill Fox Community Champion

If you are using Agile boards the versions and current sprint can be made available to anyone who has browse permissions for the project. The ability to look at all version and sprint definitions are wrapped up in the more general project administration permission.

Ah in which case you are likely to be recommended to upgrade. But I would contact Atlassian Support now to see if they can assist with resolving your current position.

What version of JIRA are you using? There are known issues with bulk changes on some earlier versions of JIRA - see for example the ticket https://jira.atlassian.com/browse/GHS-11025. If you are on an uptodate version I would suggest this should be escalated to Atlassian Support.

Hi @Marcelo Richter If you can define a quick filter for your items that do not fit in the normal release process you could still use my suggestion above to have regular releases. But this would only be used for the issues that meet the criteria of your quick filter. But as you said moving issues to a status outside the…

If you want to retain the method of working with a single Kanban board you could name your releases on a regular calendar cycle so it was not related to a specific project but to the point in time in which the work was completed. For example March release - would be marked at the end of the month WW9 - would be marked at…

See the previous answer at https://answers.atlassian.com/questions/193260

You will need to have a 10 user licence for JIRA core, and a 50 user licence to cover the Development and QA teams.

Voted for it too. Hope this gets resolved soon.

Your query requires your subtasks to also have the fixVersion completed in order for it to work. You would need to use one of the plugins to extend the functionality of JQL to allow you to query the values of the parent issue.

Hi Shilpa The way to approach this is to think about what you want to report to management. Then build an issue filter with the appropriate JQL to identify those items then display the filter in a gadget on the dashboard. So to take the example of "Report in a pie chart which projects have issues breaching SLA for issues…

Hi Shilpa Sanil There are not yet any specific reports available that are specific to SLAs (watch for future announcements as this was mentioned at Summit 2016 as a forthcoming functionality). However, having said that you can use the existing gadgets by using the SLA functions in JQL. See…

If you have JIRA Service Desk you can track all of these by creating metrics for each action you wish to track. If you do not have JIRA Service Desk then you will need to write scripts (and have a scripting plugin installed) to capture the changes on the transitions and record them in a custom field.

Hi Ambika Seenivasagam You may like to follow the progress of this ticket. (https://jira.atlassian.com/browse/JRA-7266) You will see this is already in Beta and will be released to both cloud and server. Hope this helps and please vote to increase the level of interest in the issue. Phill

The article at https://confluence.atlassian.com/jira/configuring-file-attachments-185729586.html tells you about how to configure where your attachments are stored. Assuming no changes were made on your original system you should find them in the default directory location of data/attachments subdirectory of the JIRA Home…

Once you have reviewed the contents of the migration hub as above you can then start with this page to determine the sort of upgrade you wish to do. https://confluence.atlassian.com/adminjiraserver070/upgrading-jira-applications-749382701.html Regards Phill

Hi It is virtually impossible to give theoretical estimates on upgrade times as every installation differs in lots of ways. For example you have given no indication of how customised your instances are nor which plugins are installed. However, as long as you have a non-production environment that matches. You should be…

Further to the answers from @Tibor Hegyi [META-INF] and Vasiliy Zverev I would suggest you amend the workflow to allow you to edit closed issues (you can and probably should revert this once you have made your change). Then use the bulk edit feature to select the issues you want to update the priority on and make that…

You only need to wrap in "" if the content could contain a comma.

You only need to include Parent ID if you are creating subtasks and this is where you would put the key of the issue which this is to be a subtask of.

If you are using the CSV import file to create new issues then you need to put the correct text in the column for Summary. If however, you are using the CSV import file to update fields other than the summary then you should leave the summary empty. Quote from Atlassian documentation on updating. Importing a CSV to update…