Whenever someone hears the word ‘meeting’, they think of boring discussions, where a lot of time is wasted. Usually a few emails are sent beforehand and afterwards there is an email with the minutes – which no one is going to read before the next meeting. But with an intranet, meetings can be well prepared for, executed and followed up on.
Atlassian has a public JIRA instance where everyone can add feature wishes and vote for existing ones. They close duplicates and link to the original wish if you are asking the same as someone else. They comment on issues and help phrase wishes in a way that reflect the software deficiencies and needs of customers. And they let you and me vote for what we want the most. If Atlassian could fix all bugs, they would. But they can’t. So they have to make choices.
Most employees do not use their company’s intranet. There are multiple reasons. The worst and most important is, that these intranets do not offer any significant value to their job. That’s devastating as most projects have started with different goals. Employees often describe their intranets as old and stale. This post talks about how this happens.
A growing number of big corporations is using Linchpin as their intranet technology. There are some, that simply want a fast and reliable result. But others really put a focus on preparation, concepts and a thorough strategy for the intranet rollout. Right now we are in the middle of preparing an employee survey for a new intranet project and this is my effort to contribute to the conception phase and also help you plan your intranet better.
JIRA Service Desk is Atlassian’s help desk solution based on JIRA. It assists service and support teams in integrating inquiries in a systematic process. Here you can learn about the new developments of JIRA Service Desk version 2.4
Within a company there can be many approaches for the development of texts as well as the sharing of texts for further revision. We could, for example, write a text in Word and then load the final version into the enterprise wiki. We could also send around texts by e-mail, asking colleagues to read them and, if necessary, to make changes. But we could also develop a text directly within a wiki. What should we think of this particular work process?
Within software development there are distributed version control systems, with especially git currently most popular. More and more teams are recognizing the advantages of DVCS and migrate from central version management. The market offers numerous products which enable teams of developers to manage their git repositories. All have their advantages. The most mature and most feature rich solution for an enterprise is in our opinion Atlassian’s Git repository management system Stash. We have collected 99 reasons, which all are argue for Stash and show why it is reasonable to test Stash, regardless whether a transition to Stash in the planning or has been started. 99 reasons – none longer than a Twitter tweet.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationContact
Our Sites
News
Auszeichnungen
