Vickey Palzor Lepcha Expert

Why not move over to SLACK, TEAMS or HIPCHAT ? Microsoft has announced already that Skype isn't the future anymore. Also SLACK - TEAMs offer more than Skype now.

If that is the case - I'd suggest you connect with Atlassian Support - have a ticket raised and they will look into it.

Does your security services or firewall have any restrictions that could prevent your jira server from connecting to internet or specifically to bigpicture website ?

Hit button again - but this time, before you do it , open your log using tail or similar utility and see what the log says .

What is the problem ? Any error that you encounter ?

What database is it trying to connect to ?

Hi, Please check the following link; https://confluence.atlassian.com/doc/confluence-security-advisory-2019-08-28-976161720.html

Thanks mikelj - I used /trello search and it work absolutely fine. Much Thanks.

As pe the work flow , it does seem to be following what has been setup. Can you show me what status is mapped to Kanban Backlog ?

Go to Board Settings and Disable " EPIC PANEL"

JIRA issues from one version - should not be imported into a JIRA running another version. 1) Upgrade your JIRA first from 4.4.5 to 7.13 ( this will involve multiple upgrades) 2) After your source JIRA version matches with destination JIRA version - export the projects 3) Import it to your next JIRA. ALWAYS USE EXPORTS…

Looks at my screenshot below - I have marked " SET RESOLUTION " on all my COLUMNS - so all my issues have strikethrough as shown in the other screenshot

Can you share with us a screenshot of your workflow and board settings - columns 

Jill - I guess you have two types of users . 1) Internal JIRA Directory Users - you have the ability to edit and deactivate them. 2) External Directory Users - your organization may be using an active directory which is used for user management, which does not have those dots. You might want to contact admins who…

If you are a JIRA Administrator with Admin Permissions ( not Project Admin ) - you can browse over to the admin console - select User Management , look for thr user and disable the user.

My assumption is that if you fix the collation issue - the other issue should go too.

Deactivating Users is a better option.

Are you viewing them on a board - SCRUM or KANBAN ? Have you checked your board - column settings ?

Can you open and check your project workflow and verify as to when you re-open an issue what should be it's new status ?

Opening lines for JIRA DATA CENTER Supported Platforms ; " Supported operating systems, databases, etc., are the same as for the Server installation, and you can see them here: "

Hi, Please review your wprkflow - check if Open Issue has a Transition from ALL.

Review your workflow.

You as well Sascha - your organization needs a JIRA upgrade to atleast 7.2.7 for now if not higher. Safest bet for you is to move to 7.2.7 as it seems to be fixed at least in that version BUT reoccurring in higher versions.

Why not just use the filter ? 

And it looks like this has reoccurred in many new/higher versions too despite fix in 7.2.1 . If yours is also the case, I'd recommend raising a support ticket and logging your case too though it seems to have been reported already by many.

Check your JIRA Version - it should be resolved if you are running JIRA 7.2.7 and above.

It looks like a bug to me - can you check this link ? https://community.atlassian.com/t5/Jira-Software-questions/Issues-moved-from-backlog-to-sprint-return-to-backlog-after-page/qaq-p/687353 

Hey Sascha, Can you give me a view of your Project backlog ? This is a very strange issue you know - did you try logging out and signing back in to your JIRA ? Also a good clean up of your browser cache ?

oh I think I misunderstood you ; You mean you added an issue to a sprint using right click from backlog - sprint details show up in the issue details but you find it back in the backlog instead of the sprint - is that right ?

We might want to validate that the filter query includes that particular issue which isn't visible in the board .