Vickey Palzor Lepcha Expert

To be frank - Mexico is an addiction. I lived there for 22 months and never missed home . I would love to continue there but I had other issues back then. Yet I would love to return any fine day.

Have you verified permission schemes ?

Enable Backlog on your BOARD first - after that drag the above HOLD status to backlog - so any HOLD status issues will go to BACKLOG. But like Jack said - is your backlog enabled ?

If you want to do it manually - you can just go to users management , list out all groups and see it on the extreme second right column " DIRECTORY" - lets you know if it is local group or AD group.

I'd prefer LDAP filter on advanced settings for advanced users and groups.

Nope - you should have a BROWSE option even on a CLOSED ISSUE

@Nic Brough -Adaptavist- Hey, I've been noticing this for something that whenever we share a url , clicking on it gives us 404. We need to manually edit the url address up until .html and hit the page. Not sure if it is Atlassian issue.

@Damian Camarasa Good to know it was resolved - any idea what was the root cause and what was done to resolve it ? I'd love to know :-)

@Paz Thank you for the images - workplace looks amazing .

@Damian Camarasa Did you find help Damian ?

I'd love to know more on how you implemented it. I am new to Splunk - I have no idea where to start .

@Damian Camarasa Oh! you are using JIRA Cloud ? I think Damian you should raise a ticket to Atlassian then .

poco jaja. I think it should take 5-7 minutes. You can do it - it will not have any impact.

Mucho gusto :p Can you tell me the number of issues you have in this project ? I can give you an estimate time as per my experience :-) Yes - you can access the board during this time, no problem. When you do a complete JIRA Jira Indexing ( with foreground ) - that time you will not be able to access the board. Project…

@Damian Camarasa Are you from Mexico ?

For sure you can - and the reason I said " project " re-indexing is because I do not want you to reindex other projects in your organization. :-) No - there is not risk , don't worry. Depending upon the number of issues in your project it could take its time to complete . I hope you are the project administrator :-) 

@Damian Camarasa Can you run a project level re-indexing ?

Lets do a thing - can you attach screenshots of both the method? Also I hope you are in the same project and board :-) I checked mine - they seem to be fine and behaving as expected.

Did you make changes to your Issue Type for that project ?

@Manon Soubies-Camy Simple and to the point - thanks.

@Laura Good Read. 1) Upgrade of Staging Environment is always advised - I do that all the time. This is possibly the best way to check how upgrades would go. I have been able to prevent a lot of issues from flowing over to Production. 2) I'd recommend a refresh of Staging Data using Production Backup - maybe you meant the…

@Padmasree P You are welcome.

Add the following line in your setenv.sh where you jvm argument is defined ; -Datlassian.plugins.enable.wait=300 This will give 300s for your plugins to start. Make the change and restart. If you are on windows - change it on setenv.bat And yes - check the log when it is restarting, you will see how many plugins get…

Looks like your plugins have not started completely - add an argument in your setenv.bat or setenv.sh and increase your plugin load time - maybe 500s and see how that works.

https://confluence.atlassian.com/adminjiraserver071/migrating-from-jira-cloud-to-server-applications-802592270.html Try it again - if it doesn't work, just wipe out everything on the url after .html and reload

umm under your home directory ...would look something like this; .........\application-data\confluence\attachments\

Try restoring Attachment separately - don't make it a part of your backup. After you restore your confluence - try copying the attachments separately to your new server.

I hope your GROUP Filter is not blocking the new name from being synced.

I did a couple of quick changes - ran syncs and it worked perfectly fine.

Also - I hope you've changed the group name correctly in AD - both " Group Name " and " Group name ( pre-Windows 2000) " Changing Group name ( pre-Windows 2000) alone won't work.