Thomas Schlegel Community Champion

Hi Nick, I would not remove Button A, since this is a System behaviour. BTW, I think you cannot remove this button out of the box. If your workflow transition is doing nothing else than assigning the issue to someone else, I would remove the workflow transition. In my opinion of a workflow, assigning should be no…

Hi Nick, the visibility of the workflow transition is not controlled by the permission out of the box. You have to set a workflow condition to the workflow transition. Set a permission condition to the workflow transition…

Hi Nick, the buttons are your workflow transitions, you have to look at your workflow to identify, why there are these buttons. Among other things, "Assign isue" controls the visibility of the "Assign" Button on the left side of "Comment". This is not visible in your screenshot, so I think, the permission is set correctly.…

Hi, we have done something similar: - create a group A. In this group, there is everyone who should see the space except the one person that should only see the single page - Group A and "the one" get permissions for the whole space - Restrict every "first level page" to group A, so "the one" could not see anything anymore…

Hi Andrew, we had exactly the same problem. Unfortunately we did not find a solution. We dropped the user from the internal directory and created him again. Before dropping the user, we had to change all the issues he created and where he was the latest assignnee. After recreating, we assigned the issues back to him and…

Hi Thomas, there's an old issue for that: https://jira.atlassian.com/browse/JRA-12400 Vote for it and hope, someday it will come true ;-) Best regards Thomas

Hi Robert, you do not filter out projects, but status of issues. Add something like "and project not in (xxx, yyy, zzz)"

Could you please explain your question a little bit more? I don't understand, what you're asking for.

Hi Paul, try this: {noformat:nopanel=true} ${installdir} {noformat} Best regards Thomas

Look here: https://confluence.atlassian.com/display/JIRA/Restoring+a+Project+from+Backup

Hi Kirsty, yes of course. Look here: https://confluence.atlassian.com/display/JIRA050/Importing+Data+from+CSV Best regards Thomas

Hi, you should not use the group "users" to manage project permissions. In general, the group "users" is used to control, who can login to Jira or not. Project specific permissions are given by permission schemes or project roles. In your permission scheme, give the "Browse Project" permission for example to the project…

ok, now I think I understood... Try that: issuetype = Bug AND priority = Critical AND status was in (Open, "In Progress", Reopened) on 2011-03-13 AND created >= 2011-02-13 AND created < 2011-03-13

This should do it: issuetype = Bug AND priority = Critical AND status was in (Open, "In Progress", Reopened) AND created >= 2011-02-13 AND created < 2011-03-13

But if I think of it for a while, it is not necessary to ask for the status. The only relevant thing is, that the creation date is between 2011-02-13 and 2011-03-13. Every issue that is created then was in status "open", of course...

Hi, you can use "status was" Best regards Thomas

Hi Kirill, as JIRA administrator, you can set a default Homepage: https://confluence.atlassian.com/adminjiracloud/configuring-the-default-dashboard-776636251.html

You're welcome :-)

Hi Jim,Have a look at this site: http://confluence.atlassian.com/display/DOC/Migrate+to+Another+Database Best regards Thomas

Hi Cornelius, I don't have an answer, but I think, you should contact Atlassian Support with this: http://support.atlassian.com Good Luck Thomas

look here for how it is done: http://confluence.atlassian.com/display/JIRA/Configuring+Project+Keys A little bit usage of google should guide you to perl regular expressions.

Hi, I would not do this. This can result in real trouble. Look at the last comments on http://confluence.atlassian.com/display/JIRA/Configuring+Project+Keys Best Regards Thomas

Hi Stacey, there is a workaround described here: https://answers.atlassian.com/questions/41472351 But I didn't test it.

Hi, look at these questions: - https://answers.atlassian.com/questions/66337/permissions-confusion-wrt-assigning-issues - https://answers.atlassian.com/questions/53411/can-we-control-assign-to-me-button Maybe you can get some more information about this issue. But I don't know, if you can do anything about it, as long as…

Hi James, what happens, if you slide the switch in the title bar to enable / disable the left navigation tree ? Did you upgrade your Browser ? Cheers Thomas

Hi Robert, your question was already answered here: https://answers.atlassian.com/questions/242092 Thomas

that's what I meant with "the user in "Approved By" is the only one who is able to click on the transition" Make two transitions as I suggested and everything's fine 

Maybe this works (I didn't test it, but it should work) * First: precondition: User is in field "Approved By" * Second: Validator: Field Approved is set to Yes With this approach, the user in "Approved By" is the only one who is able to click on the transition. You should add a screen to this transition, where the user can…

Hi Tej, I would make two workflow transitions out of this: * The person in "Approved By" clicks a transition called "Approved" As precondition, you can check, if the user is the one from the field "Approved By" * The next transition has a precondition that checks, if the custom field "Approval" is set to yes.

Hi, Every user that has "right to use", normally associated with the group "jira-users" needs a license seat, whether he/she is allowed to read or write. Cheers Thomas