Vickey Palzor Lepcha Expert

@Matthias Fleschütz Matthew - I'd just like to correct myself. I was talking all the time about JIRA. Ok - now getting back to Confluence. I just did a rename of Group in AD - reconfigured my GROUP Filter, my new group was created in Confluence and the old group removed as it is no longer in AD.

Sync - if there are 40 objects on AD , it would show up 40 in JIRA too ( based on filter) Out of 40 - 1 gets a new name , JIRA syncs it - strikes the old name ( non-existent) - creates the new group. JIRA will show 41 GROUPS now - but still 40 are active - the one with old name stays there but remains inactive. That's how…

I'm not quite sure if that happens - it is sync in the sense that what is there in the AD shall show up on JIRA as well. I have not seen a parameter in the AD Configuration - that would actually compare and replace entities based on old and new names.

@Matthias Fleschütz Oh ! you mean you want the old groups to be RENAMED ?

I think sync should work - unless you've not reconfigured your filters. Sync works best based on your own AD/LDAP Sync filters. Obsolete groups synced already would be crossed out if not available in AD anymore - new one should sync back provided your filters are not blocking them.

@Frank Lets go through this once Frank ; https://confluence.atlassian.com/adminjiraserver071/migrating-from-jira-cloud-to-server-applications-802592270.html 

Hello Frank, I think the first move of mine would be to have either jira server or jira cloud - not both of them at the same time. If I move to a complete server solution - I'd opt for JIRA Data Center version, or if possible merge servers into one single server considering performance risks properly. If I move for a cloud…

If the user whose avatar is missing - and has commented on the issue - even that throws you 404 everytime you will open that particular issue.

Considering every issue would have at least an assignee and a reporter - so one issue will have atleast TWO avatars.

@akhil bunty Just restore you avatars back and see if you see them again. I am sure you won't.

@akhil bunty And I don't think you should title the question as JIRA Performance issue if you have avatars missing.

@akhil bunty Probably a lot of issues in that particular board of yours do not have avatars - they are missing , so you are getting those 404. Give us a view of your board and all issues in it . We can see it right on the card if the issues have missing avatars.

What are you exactly asking ? @akhil bunty

2) Can you confirm that EPIC is an ISSUE TYPE that can be created in that particular PROJECT where your board is? Like this one issue type scheme associated to one of my project does not have project - so I cannot create projects in this project and have it on the board.

Check the following; 1) Are you looking at the right panel ? It should be a on the backlog icon - two vertical bars - version and epic.

Same as me hahaha

I use to track my expenses - scheduled all issues for bills that come every month so I dont have create them again and again - I use tempo as well to keep record of all my expenses. - helps me understand my expenditure spikes.

It doesn't look like there is any option as such like we have on on-prem Confluence at the moment. Maybe there are OOTB methods - not sure.

I'd like to suggest something sort of quiz after every chapter for a quick assessment . It keeps us motivated :p

@Harish Tuccapuram Just open your Atlassian account - look for the Developers License corresponding to your Production License and apply that here on your DEV instance.

Just validate them AFTER the export

Nah nah - you've gotta make no changes. I mean just validate after your export is completed in your Dev Environment.

The progress sometimes looks like it's halt - say takes more than 30mins to move from 20% to 21% - I'd say let it be , unless you see any error , do not stop the process.

I'd say just go for a random check of all your JIRA DEV info just to ensure that nothing points to Production Data. The xml import is pretty safe - I have done it quite a lot of times. But yes, depending on your Production Data - it could take time. Mine sometimes take 2 hours to complete.

Some of your Production configurations could reflect in your DEV instance - that you can verify and change if needed. - LDAP Config - just verify -BASE url -Internal Directory Users -Application Links

You are an admin but do you have the " archive and restore project " permissions ?

Archiving is an option just on data centre version if I am not wrong - are you using data centre version ?

I don't think you need to tread that path. Under permission scheme for this project- are JIRA Administrators allowed to administer the Project ?

Board permissions may be restricting you from viewing it - but you as JIRA ADMIN can make changes to that permission just for yourself. Add the group JIRA-Administrators to one of the role ( administrator role preferably) in that project so that all JIRA Admins can see it. Or add your individual ID as a member to one of…