Peter DeWitt Community Champion

@Daxter Bels, check this document out. It covers everything you need to know about project roles. There are even drop-downs at the top for server/cloud and server version. pd

@James Liu, check your proxy and/tomcat logs for errors. As you question stands, there is not enough information to recommend anything more. If you find any errors, you can add them back here and others members can offer advice. pd

@Peter Jahn, not in vanilla Jira. pd

@Marianne Smits, that site does not resolve when running a DNS lookup. You will need to make sure the address is published in an external DNS host or your local DNS. pd

Make sure those fields are included on your view screen for subtasks. This way the data will be displayed when the issue is moved but will remain read only. pd

@Amit Samji, Take a look at the Bulk Clone addon. I think it will do what you want. https://marketplace.atlassian.com/plugins/com.lbcg.jira.plugin.pro.BulkClonePro/server/overview pd

@Kamil Tracz, It looks like your Status was renamed. I would just rename the NOT REGISTERED status to TO DO. Administration -> Issues Tab -> Issue Attributes Heading pd

@[deleted], this is not a feature included within vanilla Jira. In order to make this happen you will need to use a third-party addon. Take a look at Scriptrunner, Misc Workflow Extensions, or Bob Swift's Create on Transition. You will want to create the Story and then automate subtask creation on the create transition…

Make sure your filter is pulling in the subtasks. You may need to add the label to them as well.

@Nikhil, you'll need a workflow extension to do this. Not sure it's the best idea to move the issue from one sprint to another though. It may be better to create a new issue in the next sprint once the first is closed. Something like Bob Swift's create on transition would work. -pd

@Bryan Stephenson, Confluence seems to have this problem from time to time. Upgrading is the way to go. It usually only takes the next point update but since you are so far behind upgrade to current like @AnnWorley suggested.

@KartikA, like Boris said the validator is the way to go. I don't think it's possible to restrict the epic link options. pd

Could it possibly be because you deleted the issue instead of removing it from the sprint first. pd

@Kristof Devarrewaere, if yo right-click the card on your board you should see the option to flag or remove the flag. There is also a system field flagged that you can add to one of your screens or your card.

@Chris Lovvorn, Take a look at Jira Misc Workflow Extensions. Almost a required add-on for Jira installs. It can handle this and much more. https://marketplace.atlassian.com/plugins/com.innovalog.jmwe.jira-misc-workflow-extensions/cloud/overview pd

We had to do the same. It would be nice if the fix version was global across projects.

@Shib Saha, Here is the Atlassian document referencing your question. https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html

@Arthur Bosch, take a look at Team Calendars.

@Roland Schuler, make sure the account you are using for the mailbox has access to Jira (it's in the Jira sers group.)

@Sebastian P, I would recommend migrating to the new server and then upgrading the DB. If you take this approach, you will be able to leave you current production server ad-is and have a roll back should anything go wrong with the move and upgrade.

@Abraham Georges, The triggers are going to be used when Jira is linked with other Atlassian Apps like Bitbucket, Fisheye/Crucible. The conditions are going to be used for limiting the transition, for example the currently logged in used must be a member of the developers group. Validators will check to make sure something…

@Mark Nelson, check this support ticket out. It looks like they closed it for a previous version but I'd open a new one for the current version. https://jira.atlassian.com/browse/SRCTREEWIN-495?workflowName=SourceTree+Bug+Workflow&stepId=6 pd

@Judy Matzkin, I was noticing a problem with this in cloud this evening? Is that what you were referring too?

@Abraham Georges, Welcome to Jira and the community. Glad to hear it's making a positive impact. As far as default automation in Jira goes, it's pretty basic. You are looking to do some advanced stuff with the auto transition and automatic email notifications. These are going to take some add-on extended functionality.…

@C Streic, Mandatory drop-down = no 'none' option. Non-mandatory drop-down = none option. As far as the second part goes, try customizing the field description in the field configuration scheme to explain to the users that they should only select two options. Hopefully they all read and follow. ;)

@Anthony Magenot, Assuming that not all of your investigative tickets make it to development tickets, it may be best to keep them separate. This will keep all your sprint and release reports clean. What you could do is create a custom issue link that is specific to this scenario and more descriptive than the default ones.

@Karl Hildebrandt, Think of these projects as Epics. If you use the Epic to represent your project you can easily attach issues across all projects in the system that are related. This allows each team to work in there own project with their own workflow process but still ties everything together. When using this approach,…

Robo Rally is a great one too. I had to buy one a number of years ago on Ebay as it was out of print.

Easy for me: Settlers of Catan .

Make sure you configure the server.xml file. Step 3 for the link above.