Matheus Fernandes Atlassian Team

Also, what is the ordering of the post-functions? You have to set it right after the "Create Issue" post-function, if I'm not mistaken.

This can be achieved by setting up a Update Field post-function in the Create Issue transition of your workflow and setting it to update the Resolution field. Basically, you'll need to: * Go to Administration » Workflows * Click the link for the workflow in 'Steps' column * Click 'Open' link in the Step Name column * Click…

It is not possible to 'deactivate' a JIRA user in JIRA OnDemand as per the Restricted Functions docs. Instead use Atlassian OnDemand's application access features to restrict a user's access to one or more applications in Atlassian OnDemand. Also, make sure to remove the user from any groups so he won't receive…

Since JIRA 5.1, JIRA administrators can 'deactivate' a JIRA user, which disables that user's access to JIRA. Also, a 'inactive' (deactivated) user does not count toward the license limit, so you can create another account in its place. You can see more about this new feature in the JIRA 5.1 Release Notes.

Hi Victor, Could you attach the rest of the error, just to be sure? I've seen similar errors where this happens due to the Field Security Plugin. It is possible that the version installed in your server is not compatible with JIRA 5.2.7 - to fix this, simply upgrade the plugin to version 1.4.12_52. I hope this helps! :)

Those should not be changed, the user_key should always remains the same. In order to maintain the integrity of the database I'd definitely advise you to use REST or the UI. :)

Nithin,The thing is, not all of those will need to be changed. Most of those are associated with the user's user_key (from app_user) and not with the user_name from cwd_user. That's likely the reason this is breaking.

Actually, there is also data on app_user. Still, I would not recommend doing this - rather, modify these usernames by editing the users in JIRA. If multiple users need to be edited, use a script to update them through REST: https://docs.atlassian.com/jira/REST/latest/#d2e4140

Indeed JIRA does not work correctly with Opera, and I'd advise you to use another browser to access JIRA as Opera is not one of the supported browsers (see Supported Platforms). There is a feature request to add it as a supported one, but I don't think it will be added any time soon (JRA-23096).

Andrey, What browser are you using? And in which version? Cheers

What if you try something like: (component is not EMPTY OR component is EMPTY) OR project in (ALL, YOUR, PROJECTS) or replace 'OR PROJECT' with any other criteria

Hi Kurt, If redmine is behind SSL: * Try to access Redmine directly through HTTP instead of HTTPS; * Or use SSLPoke to see if JIRA can connect to Redmine as per this KB (see the resolution section). * Or simply import the certificate into JIRA's keystore and try to import again. I've also seen a similar problem in a topic…

Andrzej, When you install JIRA you should see your Server ID by selecting I have a JIRA key on the setup wizard: server-key_JIRA7_install.png You should use that key to update the license details

To do it, you just have to set up the CC Assignee option in your mail handler. If the user does not have permission to assign the issue, the issue will still be created, but will either be assigned to the default assignee or will be left unassigned. From the Creating Issues and Comments from Email documentation: Select…

Perhaps JIRA is having problems receiving the ACK from the mail server confirming that the email was sent, and therefore keeps sending the email - similarly to what's described in this doc. Try checking the logs inside your jira-home/log folder (outgoing-mail.log) to see if there's anything there that could indicate why…

You can possibly remove this by using some scripting in the Announcement Banner. However, before doing so, you'll need to ensure all users currently are showing all fields. By removing the button, if the users have configured to only display certain fields, they won't be able to switch back to show all fields. Anyway, if…

Anytime! :)

That depends on what you mean by 'copied to Instance B'. If you're planning on copying the instances using a database backup or an XML backup (JIRA's native backup utility), the IDs will remain the same. If you'll simply recreate the same thing on the new instance, the IDs will be different (except for the Users,…

Hi Mark, The numbers you mean are actually the IDs of the Project Roles. The IDs will be the same throughout JIRA, not matter which project. You can see this with the following query in JIRA's database: SELECT id, name FROM projectrole; For example: id | name-------+------------------------ 10000 | Users 10001 | Developers…

The order will always follow the order defined in the Resolution page (Administration » Issues » Resolutions) page (there is a "order" column) http://jira-address/secure/admin/ViewResolutions.jspa

Hi John, You should get your license from my.atlassian.com. If you don't have one yet, you can either create an evaluation license there or you can purchase one. Also, you can see more info on this on http://www.atlassian.com/licensing/purchase-licensing. I hope this helps. :) Cheers, Matheus Fernandes

Conor, Try setting up the application link using only OAuth as the authentication method, and make sure that you have proxyName and proxyPort in both JIRA's and Confluence's "server.xml" files (see How to Configure an Outbound HTTP and HTTPS Proxy for JIRA) even if you're not actually using a proxy. I hope it helps!

In this specific case, the My Open Issues filter doesn't actually display issues based on the "Open" status, but if the field is resolved or not. That is, this filter searches for the following, not the status itself: assignee = currentUser() AND resolution = Unresolved What Renjith mentioned is that the resolution should…

Marshal, it's definitely possible to move an issue from one project to another, see https://confluence.atlassian.com/display/JIRA062/Moving+an+Issue. That being said, the backlogs are filtered using the board's filter, so as long as the filter from the other board picks up the change the issue will appear in the second…

From this menu there is no way to control what will show up. :( However this should not present any problems to you as clicking on Test Sessions will prompt for login, and dashboards will take him to the System Dashboard (which you can define as you want).

What menu items you mean?

Hi Zaridan, I'm suspecting that you are referring to jira.atlassian.com, right? Basically, to see an issue an user needs only the Browse Project permission, so you'd simply need to grant that permission to 'Anyone' (Group), which would make the issues in the projects using this permission visible by anyone (even users not…

Steve, You can get in touch with Atlassian Support through support.atlassian.com. Cheers, Matheus 

Hi, guys. This was reported as a bug on https://jira.atlassian.com/browse/JRA-43888 I'd advise you to add yourself as watchers to the bug report to receive any updates on it by email. The workaround is indeed to: Workaround * Find all the projects with the same problem from JIRA Administration -> Projects * Go to their…

I have just tested it locally on JIRA 6.4.5 but it worked without any issues. Try using the Refresh Client Resources link on the Look and Feel page and see if it helps!