Walter Buggenhout Community Champion

Hi @Alana Fernando, Yes, that is what the Jira Cloud Migration Assistant is for. See this support article to learn more about the process. Also, I would recommend you to have a look at the cloud migration guide to get a decent overview of overall things to consider. Hope this helps! 

Hi @David Huang, If you really want to stop using the email address, start communicating to your users today that you will stop using email support. Announce in time that you will be switching to portal support. Assuming that you no longer want people to send you mails, I would use the out of office / auto reply features…

Hi @Jennifer Mancke, Advanced roadmaps (and roadmaps in general) is built around the principles of the iron triangle of planning, where you have a certain scope, one or more teams to deliver and your target dates over time. Support work is not well suited to be managed through a roadmap, as it is unplanned work by nature.…

Oh, or make sure that you have the level selected in the hierarchy filters just above your roadmap:

Hi @Michelle Chu, As the message says, you'll need to configure it in Advanced Roadmaps hierarchy. Essentially, you'll need to add an additional level in the issue hierarchy above Epics and link your initiative issue type to that level. Check out this article, custom hierarchy levels to learn where you can find those…

Hi @상욱 안 , There is nothing wrong with your account. There are limitations on the basic roadmap. Progress is based on issue count (not estimates) and as such not relevant to stories (it is 0 or 1). Also, date ranges are not displayed for stories, only for epics - see JSWCLOUD-18668 for that. However, on the premium plan…

Hi @Hieu Phan, As @Brant Schroeder points out, Proforma fits like a glove to your use case. It lets you create forms that can be sent to users at a specific step of your workflow. And if you're planning to use Jira Service Management to interact with your users, you are otherwise very limited in offering input field to…

Hi @Myles.Hattabaugh, It seems that the Epic Name field is either not filled out for your epics or for some reason not or no longer visible. Regarding the first issue: unlike any other issue type in Jira, Epics both have a long and a short title: the summary, which is the regular issue title. And on top of that the Epic…

Hi @eleanor kerman, There is many different ways to show Epic progress in Jira Software. A lot depends on how you work and what your approach to that is. If you are working in a company managed project, there is a progress indicator in the epics panel in the backlog of your scrum or kanban board for each epic: As you can…

Hi @Olga Toverovskaya, There is an issue updated trigger available. Check out Automation for Jira DC/Server documentation and scroll down to find the issue updated trigger. You can specify a JQL condition further on to limit the selection of issues to apply further actions on. Hope this helps!

Hey @Ariane Voorbeijtel Cannenburg, If possible, could you share a screenshot of what you and your users are seeing? I am currently thinking of 2 possible options: * In your advanced roadmap plan itself, make sure that the hierarchy levels being displayed are set correctly also for your users (so they are not accidentally…

Hi @Gonzalez Agudelo, Diana, For requests like this, the best thing you can do is to reach out to the vendor directly (for Zephyr, that is Smartbear). From the marketplace listing of the app, you should be able to find a link to create a support request with them directly. Hope this helps! 

Great discussion topic @John Funk! I'm still on the doorstep to start familiarising myself with all these new things. I'm sure that picking a favourite is strongly related to one's role. I am really happy to see that Atlassian finally found a way to uplift Jira Core to something that has actually real value for business…

I'm supported big time by my little assistant Cloudie, who also willingly stepped into the photobooth 📸

And it's a card, yes it's a card full of stars! 🎼 🎸 🎹

Hi @Claire Maynard, Your talk on Point A was my personal favourite during the live broadcast of day 1. We all love to see more of what's new, so the overview of all these new and shiny things definitely sparks attention. And the Point A program itself is a potential game changer, I believe. With all the thrills and buzz…

Hi @shiva, Translating custom field names is not something with a major impact. A custom field has an ID behind the scenes, so the field remains the same. Just as a best practice tip: be consistent. Jira has a set of system fields that you cannot translate yourself (fields like summary, description, resolution etc). For a…

Hi @Núria Recasens, Since you did not specify the hosting type of your Jira instance, I can only assume from your question that you are on data center or server and that batch email notifications are configured to send updates at regular intervals. That is the most logical explanation as to where you aren't getting…

Hi @eleanor kerman, This is functionality from Insight, the asset management tool included in the premium plan of Jira Service Management. As of now Atlassian is primarily investing in integrating the product in JSM. It seems it will be possible to include an insight custom field (an object, as you reference it) in Jira…

Hey @Noah Shunfenthal Can you check if the fixversion field is on the edit screen that is associated with tasks in your project? Through Project Settings > Screens, locate the screen that is linked to the edit operation for tasks. Click through to edit that screen and make sure fixversion is on it.

Hi @Noah Shunfenthal, There is probably 2 things you will need to do here. The first one is easy: to remove the task from the release, just locate the task and remove the release from the fixversion field. A second thing - to bring your task back to your kanban board, I would not be surprised that you may have to update…

Hi @Maja Aagaard, Are you sure your project is a team managed project? If your project is Company managed, the feature is available, but as a setting in your project's board. Have al look at the documentation on company managed projects on how to enable the feature there. Hope this helps! 

Hi @Bruno Sergio Pongetti Goldemberg, Have a look at this related question - the approach is a bit different as how you are trying to set this up, but it might be a better fit to what you are trying to do. Essentially, when you create an issue, assigning it to the currently active sprint is an available action. Hope this…

Hi @Sylvain Viole and welcome to the community! Could you clarify your question a bit more? I am guessing you are struggling with permissions to a Jira Software project. However, as you mention product in the title of your question and space in the description itself, I am a bit confused what you are running into here. If…

Hi @Brant Schroeder, User limits are currently the same on all plans, but while you mention the move from 10k to 20k supported users, behind the scenes Atlassian is already working towards supporting 35k users per site. I am quite sure we'll see those numbers grow over the coming years on several occasions and see the…

Hi @DSell, You are right that this is not consistent, but it works like that indeed. There is no configuration afaik available to change that behaviour. You more or less answered your own question there: dragging and dropping from backlog view works really great if you want to assign a ticket to a single fix version. If…

Hi @Stefan Peruzzi, In te diagram view of your workflow, just click on the status you want to allow transitions from any other status to and then from the popup window select the option allow all statuses to transition to this one Hope this helps! 

Hi @prashantgera, As of now, migration of next gen projects between cloud sites is not yet supported 1-1. In This support article currently available strategies and workarounds are listed. Maybe it is interesting to know that Atlassian is currently working on a migration assistant to facilitate cloud to cloud migrations. I…

Hi @Paul Porter, The FixVersion custom field is where you manage your releases. You can add multiple versions there out of the box. Moreover, it is mainly your stories inside your Epics that your release. So primarily you would assign releases to stories rather than epics. But there is nothing wrong with assigning the fix…

Hi @Tali.Bartal, If the answer helped, could you also mark it as accepted? That makes it easier to find for users having similar questions!