Phill Fox Community Champion

Hi Juan, This is a screenshot of what you should see if you have the right permissions/contexts. image2015-12-22 9:33:54.png However, there are some known causes for this not to be the case. The first test is an easy one do you have permission to edit the issue? After that please…

As you did not say which version you are on I will point you at a couple of reference points. For version 6.7 and earlier https://confluence.atlassian.com/agile/jira-agile-user-s-guide/working-with-epics/completing-an-epic For version…

Hi Mazen Hassan When you say export the report what format are you expecting to export it in? If a sharable pdf is all that is required then you should be able to use the standard print functionality in your browser (as long as you have a suitable PDF print option installed). If you want to have some other format of export…

Portal only users do not require a licence.

You can find many of the translation files at https://translations.atlassian.com/dashboard/dashboard?lang=fr_FR for different Atlassian products but unfortunately not one for JIRA Portfolio.

As of 13th December 2015 this can be enabled through the application configuration. However, as this is currently a labs feature this setting could change in the future.

Hi Shawn Stevens One approach to this is to have a hidden field which is automatically incremented on a self-referencing transition in your workflow. You would then only show the approved transition when this hidden field contains a value of 5 or higher. There are lots of extensions you can write to this process including…

Is the issue only with clone or are you also experiencing other connection issues? You might wish to review the steps in https://answers.atlassian.com/questions/38070040 where the solution was to update/install GIT.

So the migration from 3 to 6 retained the keys (and these were already at 49700 and up)Is it possible that some of the original issues in 3 were imported from another source? Either an even earlier version of JIRA or maybe by the use of CSV? The same principle would apply there of each key being uniquely assigned and even…

Every project will have its own sequence of numbers. I suspect that the reason why yours are numbered 49700 and higher is that several attempts were made to import from the previous instance and then deleted until the import was deemed a success. For more detail on how (and why it is hard) to reset a project key to restart…

I suggest you try the following file:/380371/3416141.msg for the location of your attachments in the JSON file.

It is also worth checking that the folder location did not alter during your server migration.

You can also look at changing the error level reporting for the plugin to provide more detail in the log file. See https://confluence.atlassian.com/adminjiraserver071/logging-and-profiling-802592962.html for more details on how to achieve this.

Cloud is currently showing 7.1.0-OD-03-048 from 30/12/2015.

And the next major release is 7.1.x

Hi @pankaj hooda Yes your SEN will still be the same but in order to upgrade you will need a current licence so that will need to be renewed.

Hi @pankaj hooda As long as you have a current support licence which is tied to your JIRA SEN (Support Entitlement Number) then you will not have any issues with upgrading as this will remain linked. Phill

Hi Gil, You could try this as a starter https://www.atlassian.com/git/tutorials/making-a-pull-request/ Hope this helps and the rest of the site too. Phill

Yes your method will work as an approach to moving hosts. I would do at least one practice run before you make the final change to ensure that there are no hidden surprises to your approach. You can use your local hosts file to change your connection to the new host whilst still retaining the same urls.

You can always use the condition criteria to restrict visibility of the button to those with project administer permission as there may be instances when you want to do that transition when something has gone awry with the automated process.

Hi If your installations are behind a proxy server then you can change the mapping to point at a maintenance page there but provide a different url/port for the system administrators to access. If not behind a proxy then there is a similar method which requires you to edit the port on which you currently host.…

Alternatively you can use ScriptRunner to make a condition for your transition which checks for the presence/absence of subtasks. A builtin script is here which shows how to check all subtasks are complete before allowing a transition to take place.…

I also find it helpful to setup a project without any issues as a template for starting from where I know which schemes are going to be shared amongst multiple projects. This allows each project to then have small amounts of customisation without needing to remember which project is the template.

Nice reference for anyone still using Windows Vista. 

Please review the previous answer on this page. https://answers.atlassian.com/questions/2883

Latest information on this new functionality is available at http://blogs.atlassian.com/2016/02/jira-software-sprint-permissions/.

As an update to this question Atlassian have started to roll out a more granular permission set for Agile. Some details are at https://confluence.atlassian.com/cloud/blog/2015/11/improvements-to-jira-software-sprint-management#

I am guessing that your business problem is something similar to -A team of individuals deal with support issues on a rota and need to have issues assigned to them when it is their turn.So the challenge is how to notify/assign based on the rota. One option I have seen working (whilst not pretty) was to have a master issue…

Yes - you would do this through a post-function script. But would you really want to do this as it would mean changing the script anytime anyone is ill or on holiday? An alternative is to have a dashboard on which all tickets of your certain type are displayed and have people review that page.

@Carlton McFarlane Glad we were able to help you resolve so quickly.