Movonte | Atlassian Solution Partner’s Post

Hello again Atlassian community, on today's Community questions, we answer Fahad Akhtar's question on "How to retrieve REST field parameters?" So, Fahad Akhtar's issue is with REST API failure for ticket input. Recently changed fields seem to be causing a hiccup, preventing the seamless creation of new tickets from the Company A end. This appears to be a field mapping issue. It's likely that when the fields in Jira were updated, the old field parameters were replaced by new ones without also updating them on Company A end. In Jira, Field ID remains same but the names could be changed hence causing an issue. The REST API defect field uses the Field ID to map the values. Here's what we suggest 🚀: 1. Open one of the previous tickets created successfully via REST. Choose the option "export to JSON" in the

Atlassian strikes again with great features and improvements! Now it's "hide actual problems under useless error messages". Love it! Just maybe a small suggestion: re-write error message to something even more vague, like: "Whoopsie-doopsie little champ! This thingamajig had a little poo-poo... Sorry about that! Keep trying what you are doing and maybe it will work sometime! XOXO Atlassian". Afterall, BitButcket is not something that is used by the technical users, so that's just forward thinking!

English Response: Hello again, Atlassian Community! In today's Community question, we delve into "Re: Re: Can I change the page source code on my statuspage?" Look no further! The Jira Service Management for Data Center does offer some customization capabilities, but direct access to HTML, CSS, or JS isn't typically provided. However, you can still customize the look and feel of your portals using the features provided. Now, when it comes to embedding a chatbot, we suggest using an app from the Atlassian Marketplace that provides this functionality. There are several apps available that can help you integrate a chatbot into your support portal. That's it for today, folks! Do you have more questions? Feel free to visit the original post here -

Automation just leveled up! ⚒️ Check out some of the new automation features added across the Atlassian suite. From natural language rule-building with Atlassian Intelligence, to more admin controls – there’s something for every team to love. Read more on the blog: https://go.atlss.in/6fna87

Learn about all the cool things we do through Automation

It's the little things like having things to look forward to or knowing you're not the only one who wants something. And for that, I like to visit the public Atlassian #Jira https://lnkd.in/gMj-HcHj where I can peruse the suggestion, known errors, workaround etc. Yes, I have spent an evening browsing these. I have also spent many an evening doom scrolling. Some may argue not much difference between those things. However when I find something of particular interest I will vote. And then I get updates. And when I got the latest update on "Ability to restrict ticket creation for certain "Request Types" I was particularly excited. https://lnkd.in/g5YbwjwK Yes, this request has been open since 2013. I know! And we certainly could throw the "It's been 84 years" meme at this well. I'm choosing to remain excited and happy that it remained in the backlog and it's going to become a reality! We all have skeletons in our backlogs do we not? Do I use the word excited too much when posting about Atlassian? Maybe. Is it really how I feel? ABSOLUTELY! Otherwise I wouldn't be here doing it. 😁 #JSM #JiraServiceMangement BTW if anyone at Atlassian reads this: When a Jira.atlassian issue is linked to from a community post, could you please add statuses to those links so it's visible from the community page? Make them a little smarter? (Community isn't one of the options to report bugs or suggestions.) Many thanks! 🙏

Hello again Atlassian community, we have a great discussion today regarding a question titled "Re: Re: Send Notification when Total Billable Project Tim..." from our user Mayra Hernandez. Mayra is looking for a way to get notified when they have reached 80% or 90% of the total billable time for a project within a current month, this time includes many issues. This can be achieved by creating a custom field that tracks the total time spent on the issues for a project in a given month. You can then create an automation rule that triggers a notification when the value of this field reaches 80 or 90%. In the issue navigator, you can search for the issues using the JQL query "project in

So, word on the street is that Atlassian's OpsGenie is about to make its grand exit soon, making way for Jira Service Manager. Now, if I were told to switch from OpsGenie—a solid product for the era it was built—to Jira Service Manager overnight, I'd be scouting for alternatives ASAP. And guess what? A bunch of savvy customers already made the leap from OpsGenie to FireHydrant, thanks to our OpsGenie migration tool (It's open source: https://lnkd.in/gF2tFfdP).

Hello again, Atlassian Community! Let's dive into today's question titled "Re: How to Add and exclude Stories based on Qurries" 😊. The question cared about how to exclude specific stories based on certain criteria in JIRA. Now, in JIRA, you can conveniently exclude specific issues by using the JQL

👍 It's true, you can use improve issue feature that is powered by Atlassian intelligence. What does it do? ☑️ Helps with writing better issue descriptions ☑️ Helps with summarizing the comments ☑️ Generates subtasks based on the issue description #AtlassianCreator #Jira #AtlassianIntelligence