Walter Buggenhout Community Champion

A free site may gets suspended after you haven't accessed it for 90 days. You seem to be convinced that you have been working in it recently, which leads to the obvious assumption that there is more than 1 site or something really strange is happening. In either case, contact Atlassian support directly mentioning your site…

Hi @Charles.Chaaya and welcome to the Community! While I am not entirely sure if notifications will be sent out, it is great that you are aware that this might indeed happen. The workflow migration is a status change and status changes may trigger notification emails. Even in case of uncertainty, you can easily disable the…

Hi @Hamza ait aissa and welcome to the Community! I am a bit puzzled as to why you would split up your customer portal across different service desks if you would want to manage all the tickets they generate in 1 service desks after all. Wouldn't it be easier then to just create 1 single service desk project and set up…

Hi @Nayana Thara B and welcome to the Community! If you can't reactivate your site via adding payment details as the link in your screenshot explains, you must reach out directly to https://support.atlassian.com/contact/#/ as they should be able to actually connect to your site and check into what is wrong. Hope this helps!

Hi @Mohamed Fouad, I noticed this question is a few weeks old. I hope you managed to resolve the issue by now, but - if not - it may be due to missing synchronisation configuration in your BigGantt app. Have a look into the app documentation describing the technical configuration of the product. Hope this helps! 

Welcome to the Community, @Alexa Markoff! 

Thanks @Craeg Strong for sharing such an extensive post. I liked (amongst several other things) the mention of the documented work agreements for your team. It got me wondering if that is an extensive list of agreements, what areas it covers and what you do as a team to define, implement and review them.

Hi @Mai Torralba, End dates on issues below the epic level are not displayed in the basic roadmap. There is a feature request for this functionality that you can track here: JSWCLOUD-18668. Hope this helps!

Hi @Scott Buratt, After activating the premium plan, advanced roadmaps has its own permission settings that must be adjusted. Maybe that hasn't been done properly yet. You must be at least an advanced roadmaps user in order to create plans. A Jira administrator can set these permissions from <your atlassian…

Hi @Tanvir Hossain and welcome to the Community! The data center version does not have this slick visualisation. Your screenshot is from the standard roadmap in cloud, but this does not exist in the on prem version. Dependencies on the roadmap in Data Center are shown as badges, as you can see in this example: For a more…

Also: be honest in your status updates. If you know there's a problem, don't be afraid to share it. Honest communication allows for timely action (if necessary) 🏎

Hi @Keith Wawrzeniak and welcome to the Community! To search for services, just use: "Affected services" = <select your service> After typing the = sign, you will get a list of services where you will be able to select the service you need. After you select that, it will turn into a massive, unreadable string of…

Hi @Drew I did not know about the link with customer notifications, but it is definitely true that a request type must be selected in order for a request to be visible on the customer portal. Basically, tickets via de portal (and evidently by customers) can only be created via those request types. The create button in Jira…

Hi @Alex Vizgard, Unfortunately, as you can read in this support article, permissions in the free plan are not configurable. Everyone who can access Jira, has project admin permissions on all projects by default and you cannot change that. Hope this clarifies! 

No, you must ensure that the auditor custom field is present on the create issue screen in the project where you want to create your issues (or on the edit screen if you are trying to edit existing issues). Navigate to the project where you are trying to create issues, navigate to project settings > screens, locate the…

Hi @Wendy Chen, Yes. As the error message says: check your field configuration. The auditor custom field must be on the create screen of the issue (type) you are trying to manipulate. Otherwise it can't be filled out.

Hi @Wendy McCurdy, Apart from adding your JSM tickets to the sprint, I don't see how you would be able to do this dynamically, since there is no way to fetch the sprint start and end dates in JQL. Still, your filter looks good. You'll just have to update the dates once every 3 weeks. Hope this helps! 

Hi @Disha Patil and welcome to the Community! It is very well possible that your subscription date has been aligned with an already active subscription, as your end dates in your subscription end on the same date. If that's the case, that should also reflect in your bill. When still in doubt, for this type of questions…

Hi @Nicholas Carter, I can imagine. That is the part where your knowledge of what you want to achieve comes in. You can play around with both the callback date you enter on a ticket and with the frequency of notifications. 

Not exactly, @Wendy Chen. I was thinking you 'd have an automation rule that responds to the issue created trigger, checks if the issue created is an epic and after that condition: new action: set variable (name: {{auditor}}, value {{{{issue.reporter.displayName}}}} And then, when you create the 5 issues in that epic, use…

Hi @Wendy Chen, You should be able to create a variable (e.g. {{auditor}}, fill that with a smart value from the epic's reporter ({{issue.reporter.displayName}}) and then use the variable to set the auditor custom field of your linked issues while you are creating them. Hope this helps!

Hi @Nicholas Carter and welcome to the Community! It should be relatively easy to use that same logic, but bring it into a tool that is a little bit more robust than Excel as a work management instrument ... 😊 You could set up a date custom field (e.g. callback date) that you can add to your service ticket screens and have…

Hi @ryanjohnsond, That you don't see epic names anymore is linked to a recent change to eliminate the double entry that was required when creating epics. You can read more about that change in this community article. Hope this explains!

Ah yes, obviously @Mark Nicoll. If you want to fix that for existing tickets, I would focus on the tickets currently in your board and set the counter manually. I would expect it can't be that many. Pretty soon, you should be up to date. About the code: these are automation smart values. If you want to do any dynamic…

Hi @Pankaj Kalambe and welcome to the Community! You actually answered your own question: a sprint belongs to a specific board. Since you are seeing your sprint on board B, it is perfectly normal that it is not on Board A, as that is not where it was created. Quite simply: you only get board reports on the board where you…

Hi @Mark Nicoll , yes of course. You'll need to tell your custom field to increase its value by 1 each time a new bug gets linked. You'll need to add this smart value to make it work: {{#increment}}{{issue.Bug count}}{{/}}

Assuming that your project is company managed, navigate to Project Settings > Screens and locate the screen scheme. that is associated with your story issue type. You'll need the screen(s) that are used for editing/viewing your issue. Click on that screen to edit its layout. You should be able to select the bug count field…

Hi @Mark Nicoll, That is a very specific use case you are describing. I can only imagine you would be able to link bugs to stories if you have very specific procedures in place around how you define your stories as well as bugs. I don't know how you could possibly link all bugs to a specific story. Rather to an…

Hi @Eddie Wang and welcome to the Community! You are sure you are in a software project and have the necessary permissions? I tried to simulate what you describe, but both in an old and a new software project, I get this view after navigating to project settings:

Hi @Ron Reish and welcome to the Community! You can set up an automation rule for that, based off the work logged trigger. Your rule may look somewhat like this: Hope this helps!