👋 G'day Atlassian Community!
For this Welcome Wednesday[1], I've got two questions[2]:
I'll start!
🙃 Please comment with your answers! Looking forward to your replies.
[1] Welcome Wednesdays are an easy way to participate on the forums, usually on non-Atlassian topics. Check out past Welcome Wednesday posts.
[2] Thanks to Community Champion @John Funk for the idea of surveying the community! One day I hope to meet him in real life.
¡Genial! ¡Gracias por compartir!
Nice! Thanks for sharing! (original English)
We're a very large Org - 15-20 Sites - the primary site has 4k Spaces in it. (Yeah - it's - it's a little busy)
Its for those moments I get asked a Tempo question. 🤪😁
HA! I'd include that under the Atlassian banner, but I get it 😭
Tempo is not Atlassian. Its a 2nd party add on. I will die on this hill! 🤣🤣🤣
(Its like tea leaves to me...but we take care of our folks. 😁🙂🙃)
Hi @Dave LIAO thanks for the thoughtful post.
1. What's your current job title? Or last job title, if you're not currently working.
2. Is your job Atlassian-related at all? (yes/no) What percentage?
G'day! @Dave LIAO 👋
1. My current job title is Senior Consultant — though in practice I'm an Atlassian Administrator through and through. Day to day it covers Jira, Jira Service Management, Confluence, Assets, and everything in between.
2. 100% Atlassian. From configuring workflows and automation rules, to CMDB design, portal customization, and even onboarding/offboarding integrations — if it has an Atlassian logo on it, I'm probably the one managing it.
😄 Love seeing how many of us end up with generic titles that don't quite capture how deep in the Atlassian ecosystem we really are! 🙃
😂 It's always entertaining trying to describe our jobs to non-technical and technical folk alike!
1. Up until now, I've been juggling two titles: Team Lead for our Support Team and System Owner for Atlassian. But as of this month, I've officially dropped the Team Lead hat and am now "just" the System Owner for Atlassian (as well as SharePoint). 🥳
2. So far, Atlassian has taken up about 50% of my time, at least on paper. 😅 Looking ahead, I suspect it'll be closer to 75-80% of my workload, if not more.
Your next objective...secretly swap sharepoint for loom/confluence! 🤭🙂
also grats on the psuedo promotion. 😁
Hah! I'll see what I can do 😉🤭
Due to the nature of our documentation, some of it needs to live separately. But my goal is to at least establish some clear guidelines on what goes where, so we're not all playing document hide-and-seek. 😅
Thanks! Looking forward to diving deeper into the Atlassian universe! 🤩
@Marita Gustavsen - "some of it needs to live separately"
Interesting, let your stakeholders know about Confluence's space-level permissions? Or let them know if you go to an Enterprise plan (assuming you're not on one already), you can have multiple Confluence Cloud instances. 🙃
We didn't have the Enterprise plan when we migrated to the cloud (we do now), so some documentation ended up being moved elsewhere as part of the migration. That decision wasn't really mine to make, and the structure and access controls for that specific content are a bit of a maze. 😅 I'd probably leave that particular area as-is for now.
The good news is that I believe it's being phased out over time, so there's a decent chance I won't have to worry about it forever. 😄
What's your current job title?
I can just say, I'm pretty happy where I am at the moment :)
Current job title: My official title is Technical Project Manager, but for each project, my involvement is different so my title is changed to align with my role in the project ☺️
Atlassian usage: 25-50%, as the documents are maintained in Confluence and the tasks are created and updated in JIRA.
My official job title is Anwendungsbetreuer, roughly translated as IT Application Specialist.
On paper, my role is around 50% Atlassian.
Fun fact: within those 50%, I administer, manage, and develop our company’s entire Atlassian stack. During the other 50%, I also look after aQrate, Check Point, Intune, Active Directory, Azure and many more.
So, as often happens in IT, the official title is much shorter than the actual job description. 😅
1. What's your current job title? Senior Systems Analyst and SME for a bunch of business applications.
2. Is your job Atlassian-related at all? (yes/no) What percentage? Yes. One of two that work on the Atlassian suite. Probably around 90% of our work is in Atlassian but we work on all business productivity applications. We have around 800 applications though. We have JSM, Confluence, Jira, Jira Product Discovery, Assets and a host of third party apps such as X-ray, Tempo, etc. The third party apps are the tricky ones as you spend a lot of time figuring out what has gone wrong as you only work on them when they are installed or break.
Huh, I had to look it up to confirm, but my official job title is:
Sr. Systems Engineer, Atlassian
HOWEVER ever since we migrated to Atlassian Cloud (May 2024), I feel like my job is also:
But generally I tell people I'm an Atlassian Admin, and if that elicits a blank stare, then Jira/Confluence Admin, and if THAT doesn't help, "I work with computers."
Atlassian is like 95% of my job.
@Darryl Lee - welcome to the Atlassian Community! I work with computers too!
I wonder what our Atlassian Support filing count is, over our whole career. I should find someone at Atlassian who can run the JQL to find all the requests filed with my multiple profiles... (ID-240)
Be bold: you're a Lightning Rod, Harry!
I love this subject. Good one!! Here I go:
1. What's your current job title?
My job title is Agile Delivery Manager and Interim Head of Data Platform depending on the audience
2. Is your job Atlassian-related at all?
Yes, I'm the business area admin and use Atlassian products for 50% to 75% of my time (this depends on when in the sprint cycle we are; first week is about 75%, second week is more like 50%)
1. Jira Business Administrator
2. 100%!
Head Toolsmith (I made it up) and about 90% these days.
I have an idea that everyone should have two titles: the one HR gives you and pays you accordingly, and one that you make up that communicates something about what you actually do.