Activity
Mon
Wed
Fri
Sun
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
What is this?
Less
More

Memberships

Atlassian Everything

275 members • Free

Conscious Business Accelerator

11.3k members • Free

8 contributions to Atlassian Everything
Users as Asset Objects
What's your use case? How did you import Users? As CSV, sync via Entra or automation? What's the attributes, or do you keep it simple?
0 likes • 1d
@Tei M. my former org had both BambooHR and then Hibob. We had Okta, so users were added via Okta Workflow into Jira, JSM, Confluence groups. Did not have users as Asset Objects, but i wouldn't be surprised if the process was the same.
New site or cleanup?
What's your preferred way of work? Especially for work or Atlassian Jira, when you inherit it all from prior colleagues. :) You like to set up everything anew and customize from there, or you rather organise, cleanup and optimise the inherited "mess"? :)
3 likes • Feb 9
@Orla Mears I've written a piece on this in Atlasssian Community. https://community.atlassian.com/forums/Jira-articles/Jira-Governance-Navigating-the-Space-Between-Autonomy-and/ba-p/3156269 Personally, I don't see how a new instance helps, unless absolutely every aspect of the instance is a mess, and everyone agrees to default screens and default 3-step workflows. It also depends on what type of mess you are in. Is it a duplicate custom fields, dead projects mess? Security groups / permissions mess? Workflow mess? Unused licenses / resources / apps mess? Not every unruly instance is the administrator's fault. For example: If you have an instance with abundance of workflows where engineering teams are using different workflows to do the same work, that's an issue with the xDLC to be resolved with an agile coach and Dev leadership.
0 likes • 5d
This question inspired me to write an article: https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/The-Three-Pillars-of-Effective-Jira-Governance/ba-p/3199351
Rest API learning resources
What’re the best/quickest ways for setting up and learning to make API requests with Jira and the Atlassian cloud platform overall? I’d appreciate any recommendations for trainings, thanks!
2 likes • 8d
I learned by doing. For me this looked like getting an API key set up and then using postman to explore the API. I felt that cloud API was a bit limited compared to DC API, and I ended up writing python scripts. one thing i found useful with the API is the jql endpoint. This one allows you to select a group of records by providing a jql and then pulling them down via api. python is then used as transformation layer to stage the data or perform additional operations on it that API cannot do
Future strategic Atlassian moves: What do you see on the horizon?
I am currently engaged in consulting a german authority regarding the DC EoL. Besides the political aspect which I do not want to cover, there is the technical aspect. What I am curious about is what kind of strategic moves do you already see on the horizon? Like the following: - Asset likely will be untied from JSM - usage based pricing: Asset objects, Rovo conversations, AI usage - push towards collections - more than the usual 10-15% pricing increase when DC is sunsetted Maybe I missed some tendencies, which are already obvious?
2 likes • 20d
For sure use-based pricing is coming on Rovo side. I think Plans will likely get built up into a stand-alone project management product that's closer to monday.com or Asana. Not yet sure how Atlassian will leverage that recent browser purchase.
3 likes • 18d
@Josh Golosinskiy That's a reasonable forecast and it makes sense. At bare-bones product & engineering level which is the starting point for many tech start-ups, there are simpler options like GitLab. Sure, it doesn't have all the bells, whistles and a thriving app marketplace, but at that org maturity level most teams just want to manage sprints and write code. Other early-stage businesses who don't write code can probably get away with simple task managers like Trello. Atlassian as a platform shines brightest when orgs mature into needing consistent, traceable, transparent workflows, and your whole org (or at least most departments) are looking for a way to run this in a unified ecosystem. Both project management and crm capabilities seem like a closer fit with the platform as it is today. Email/Messaging and Calendar (beyond what Confluence has) seem more as an outlier.
Question - How do you track work items in QA thru Prod?
My team does operations tickets (incidents, support tickets) AND new feature development. We do not have any QA people - instead we depend on our production team to do QA before we deploy to prod. We also have external customers that need to do UAT testing in our UAT environment. Issue — because we are reliant on the production team or the customer to clear QA and UAT, tickets can stall at that stage for weeks. Right now the workflow looks like this: Backlog —> To Do (Assigned) —> In Progress —> In Review —> Ready for QA —> In QA —> Ready for UAT —> In UAT —> Ready for Prod —> Done (which means Deployed to Production) So, my devs do the work and the code Review then the ticket stalls at QA or UAT for weeks waiting for the other team or customer to do their part. This time adds time against the ticket that is not an accurate reflection of my team’s work. How do you handle these things? Do you break each piece of work to a separate sub-task? (Like Development ticket, QA ticket, etc?) I’ve been racking my brain and am looking for some new ideas/suggestions. Do you break off that piece to another project so that the team’s work from to do thru Code Review is what is measured?
0 likes • Feb 21
I've been meaning to write an article on this same topic!
1-8 of 8
Artem Taranenko
3
45points to level up
@artem-taranenko-1614
Seasoned software implementation professional passionate about the Atlassian platform. For contact reach me at [email protected]

Active 19h ago
Joined Jan 13, 2026
Powered by