Walter Buggenhout Community Champion

No. Just add a condition to your rule after your Issue Created trigger to validate which project the issue is created in. That would address the correct direction for the creation of tickets. If you want to sync comments between issues, that would require a different automation rule because it needs a different trigger.…

Hi @Chris Bickley and welcome to the Community! No, not as far as I can think of. Also, while I understand where your request is coming from, it might not be fair to try and do this. Assuming that your overall plan would be to get problems resolved in - just as an example - 3 business days and 2 teams need to work…

Can you point me to the right side , how to create that multiple-project scope ? As I mentioned, you need Jira Administrator permissions to be able to do this. If you do, navigate to Global Automation in Jira Administration (can be found at https://<your jira site>.atlassian.net/jira/settings/automation#/rule-list), locate…

As long as you don't surpass any limitations of the free plan (that can be users, but also file storage, ...), your free plan remains free. But it also requires you to use it actively. Atlassian may disable a product if it is not being accessed or used for more than (I believe 90) days.

Hi @Adam Kruger and welcome to the Community, The error suggests that you are not logged into your site or have lost product access to Jira. Your question is tagged as Jira Service Management while boards are a feature of Jira (Software). Could it be that you had a trial of Jira running before the holidays which may have…

Hi @Valentin Cojocaru and welcome to the Community! Is your project company managed or team managed? If it is company managed, adding/editing issue types or workflows is not controlled by project permissions. These can only be managed centrally by a Jira Administrator. Hope this helps!

Hi @Jorge Oliveros and welcome to the Community! As long as you create that release linked to a project and then save the changes you make in your plan to Jira, yes it will. Hope this helps!

Hi @Nelson Tang, The displayed fields are not configurable at this point. That seems one of the things reviewers of the add-on are suggesting to improve, but at this point it just displays the way it is. Hope this clarifies! 

Hi @Pedro Pintado, That is not possible indeed (unless you would consider updating your project names). When you group by Projects, the groups are ranked in alphabetical order and that is not configurable, afaik. To zoom in on the selected project, you can apply a filter on the project, so you only see that one in your…

Hi @Anthony GERARD and welcome to the Community! Starting off with a small detail, but probably worth mentioning to avoid any confusion: if your auto-scheduler does overwrite certain fields, it's definitely worth having a look at its configuration and decide if you really want to allow the tool to do this. In many cases,…

Hi @Rob Horan, The short answer is: they aren't. Forms in Jira (so, without JSM) are a brand new feature. As mentioned in the community article you shared: We have no current plans to merge with the forms capability available in Jira Service Management and there will be no changes to any site which currently has these…

Hi @RG³, No, the sidebar in Atlas is not configurable. It just displays as it is and it does not have options to customise it. Also, don't expect a lot of changes there in the short future, as Atlassian is integrating Atlas features natively in Platform Experiences. That is fundamentally the same thing, but Atlas won't be…

Hi @Bailey Wolford and welcome to the Community! See this support article on how you can switch from monthly to annual billing. Hope this helps!

Hi @Mykenna Cepek, The documentation is not wrong, but comparing Forms in Jira to ProForma is not a good comparison. Atlassian acquired ProForma a couple of years ago and integrated the app natively into JSM. And indeed, if you compare that with the forms you see in Data Center from the former app, the similarities are…

Hi @Abigail Erkes and welcome to the Community! 1. you can't and you shouldn't. Done issues in a backlog would - in proper Latin - be a contradictio in terminis. The backlog is a list of items that still need to be done. So having done items in there would only clutter your view on work that matches the definition. 2.…

Hi @Nicolas SCHANG and welcome to the Community, While there is no support currently to add a child issue directly from an initiative, that parent-child relationship is present natively. You just need to fill out the Parent field on your Epic issue to link it hierarchically to its parent initiative. This does require you…

Hi @Frank Rieger and welcome to the Community! No. Jira Product Discovery is built on the foundations of team managed projects and issue level security schemes are not available for that type of projects. There is a feature request for such functionality that you can track here: JSDCLOUD-8749. But Atlassian indicated back…

Hi @Lior Adler and welcome to the Community! You tagged your question as related to the Premium product plan. That's good, because being on a premium plan is a prerequisite to allow you to do this. With Jira Admin permissions, navigate to Settings > Issues > Issue Type Hierarchy and follow the steps described in this…

Hi @Eric Roetenberg, Jira Cloud has a data copy feature available that allows you to copy projects from one instance to another. Settings as well as data are copied over in the process. As one important piece of advice: before you jump in head first and start moving things around, read through the documentation thoroughly…

Hi @PIT Solutions, For payment issues, reach out to Atlassian support directly via https://support.atlassian.com/contact/#/ and select Billing, payments and pricing. Hope this helps! 

Hi @Augusto Romaniuk and welcome to the Community! Yes. You have updated the estimation statistic of your board, but that does not do anything about the fields on your screens. Estimativa original (or Original estimate) is a distinct field that will always ask for a time value. If you want story points, you'll need to add…

Hi @Martin Pendlebury, That is as simple as it is clever: you need a way to move items from your backlog onto the first column of your board. And that's what the to do is for. It allows you to drag and drop issues from your backlog onto the first board column. Hope this helps! 

I don't know what type of field release version is - it does not look like a Jira system field as far as I am aware and so it is probably a custom field that was set up by someone in your company. If it is a supported field, you can import it into your plan from Plan Settings > Custom Fields > Add custom field. After that,…

You're welcome, @Annie Kearns ... No, the basic timeline has a nice visualisation, but it has its limitations. Issues without a parent epic are not displayed and that is something you cannot configure. So indeed, if you don't intend to put all your story or task level issues under an epic, you'll have to get them in a plan…

Hi @Zbyněk Hostaš, This external user will need a license for the Jira product the project is created in. From your description and the tags on your question, that user will need product access to Jira. There is no difference between internal and external users when it comes to licensing. Hope this helps!

Great to hear, @Claude and @claudeeller0! In that case, do hit the accept button 😛 Based on what I understand about your setup, I think the best thing you can do is either add JSM (the product) to your Jira site or the other way around, and optionally use the copy product data feature to copy over your data from one site…

Hi @Annie Kearns, These are indeed different timelines. One is coming from Plans (formerly knows as advanced roadmaps) and the other one is the basic timeline that is included with a board in a software project. Basic timelines - however - are only available if the board in your project only contains issues from a single…

That's it indeed. You probably have added a new site under a same organization (which acts as an umbrella, more or less). But in order to add Jira Software Users as collaborators to Jira Service Management, you need to have these products under the same site.

You don't need to provide billing details on the free plan. However, if you surpass the 10 user limit (or other limitations, like the 2 GB storage limit), there is a risk that your account may get suspended if you don't provide billing details then. That's a risk to keep in mind.

Hi @Yuliia Vyborova, No, that is a different field. The release you see in a plan corresponds with the fix version field in Jira. Hope this helps!