Matheus Fernandes Atlassian Team

Darin, As mentioned by Arthur, to change the PORT JIRA listens to, just follow Changing JIRA's TCP Ports. However, please note that, in Linux, all ports below 1024 are privileged ports, and therefore only the root/super users can run services on these ports. I have found a couple of articles discussing the best way to…

Hey, I know this is probably dead by now and you have possibly already figured how to retrieve this information, but I believe you could use the WAS or CHANGED operator in JIRA, e.g.: Project = TEST AND Status CHANGED TO "Intermediate" DURING ("2012/08/01","2012/10/05") Cheers, Matheus Fernandes

Hum, I m sorry to hear that, it wasn't supposed to be like this. But it seems that the DatePicker has some bugs :/ What you could do is instead of using the current date as default, is manually set the date every time you pass that screen. I hope it helps.

Hum, I m sorry to hear that, it wasn't supposed to be like this. But it seems that the DatePicker has some bugs :/ What you could do is instead of using the current date as default, is manually set the date every time you pass that screen. I hope it helps.

Please, contact me if you do.

Exactly! :)

Hi Sonalo, What you could is create a "Date Time" custom field, and on the "Operations" column, click "configure" and set the default value to "use the current date as the default", and then add it to the screen of the operation that you want to keep track. Doing this, every time you do the transition the "DateTime" will…

Also, check the configuration of the Application Links, as there is a Display URL field that may also have the setting to the incorrect port*. :)

If you want to access the project overview, simply click on the Project's Icon on the sidebar. :)

Hi Todd, As per the JIRA 6.4 Release Notes: New sidebar preview We've been working hard on improving JIRA's user interface, and in JIRA 6.4 we're giving you a preview of what we've been working on. We wanted to make accessing your project's information as efficient as possible, so we've introduced a navigation sidebar to…

Hi, Hugo. I believe this was due to an integrity problem in the database and you have already resolved this problem, right? Could you let us know what was the cause of the problem/solution so that anyone else facing the same problem can see the resolution here? Thanks!

Did you remember to publish the workflow and made sure this is the correct one? Also, this property is true automatically, so unless you have a jira.issue.editable set to false, this is probably not the problem. :)

Try removing the property entirely from the workflow step! :)

Actually, from the plugin's page, the JIRA Gantt-Chart Plugin it seems this plugin indeed needs a license (it's a paid plugin). :/

Rather than deleting a user, I'd recommend that you deactivate their account instead. Deactivating a user's account will prevent that account from being used and prevent anyone from being able to log in to JIRA using that account. However, it will preserve that user's issues history. * If you would like to deactivate a…

Hi Dieter, It seems that the filters being used by the boards are not correctly configured to filter this issue out of their boards - take a look on https://confluence.atlassian.com/display/AGILE/Configuring+Filters Basically, each board should have its saved filter like: project = 'ThisProject' ORDER BY Rank ASC I hope…

Rajani, In order to do so, you'll need to navigate to Administration » Plugin and click on 'Uninstall' next to the UPM under 'User Installed'. If you can't uninstall the plugin this way, you'll need to: * Shutdown JIRA; * Remove the upm jar file from the $JIRA_HOME/plugins/installed-plugins directory; * Restart JIRA Any of…

Hi there, By default, it is not. History searches do not support the 'type' field. In standalone you could possibly use 3rd party plugins to expand the JQL functionality, but I don't think you'll be able to do that on JIRA Cloud.

Hi, Mihail. This looks to be possible in JIRA 6.4.7: JIRA 6.4.7 Release. Cheers, Matheus 

I don't know exactly what is happening, probably looking into the logs you'll be able to see what exactly is the error. However, I've seen some issues when upgrading GreenHopper that were resolved by simply restarting JIRA and this issue may possibly be fixed by doing so as well. I hope it helps.

I've just been testing and reviewing this locally, and this is actually the expected behavior. Reviews that are still in Draft are not considered by JIRA as it is not a valid review status (Draft Reviews are not yet completed or released to the reviewers); and Summarized reviews are past the reviewing phase as per Roles…

Could you post the full request you're making to JIRA?

KB for this: How to Remove the 'Everyone' Share Option from Filters

In JIRA 5.1, this is possible to achieve by modifying the edit-share-types.jsp file, inside the JIRA-INSTALL/atlassian-jira/template/aui folder. You'll need to edit the file and modify from line 22-26, from: <select id="share_type_selector"> <ww:iterator value="."> <option value="<ww:property…

Basically, if you want to configure a workflow scheme that is shared by more than one project, you will need to do one of the following: * disassociate the workflow scheme from all other projects - which is what I believe you did, and made you change the issues' statuses -, or; * copy the workflow scheme, edit the copy and…

Try installing JIRA Agile in the instance in which you are importing the data and then importing it again

No, there is no outage when updating add-ons (the add-on itself will be unavailable in while it is updated). If it is an evaluation license or if the license is not expired, it will still work. :)

Download it from https://marketplace.atlassian.com/download/plugins/com.pyxis.greenhopper.jira/version/1870And on the Manage Add-ons page, upload it. Just make sure to upload it to both instances

Just navigate to Administration » Add-ons » Manage Add-ons and upgrade it to the same version in both instances.

As per https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+Cloud+to+JIRA+Server, try to log in using the System Administrator account (sysadmin/sysadmin)