Walter Buggenhout Community Champion

Hi @James Skinner, If I was in your shoes, I think I would definitely take more functionality related stuff into consideration than just the URL part to make a decision like this ;-). I am not a technical expert of port forwarding, URL masking and stuff like that. But I do know that each project has its own unique URL. And…

About the custom URL, @Carlos Garcia Navarro is right about the outstanding feature request and watching/voting for it is definitely something I'd recommend you to do. If this is of outmost importance to your organisation, there's workarounds for that. A marketplace app like Refined for Jira Cloud e.g. facilitates custom…

Hi James, Yes, certainly. I wasn't sure from your question at what stage you were in your exploration, so I sent you the starting point to learn more. But you can find elaborate documentation online as well. Some specific sections that may be of interest based on your questions: * Getting started / admin guide * Setting…

Hi @James Skinner, Jira Service Management should be able to support you in those areas. It is not obvious to explain all the bits and pieces, but the platform is based on ITIL principles, supports the workflows of classic ITSM processes (incident, change, service request and problem management) out of the box. As it's…

Hi @Anuradha Yadav, Technically, the main things you'll need to do is: * replace the issue type scheme from GiS to non-gis * replace the workflow scheme from GiS to non-gis * review your dashboards * disable scriptrunner scripts (if necessary) Before you do so, be aware that non-gis projects apparently are missing issue…

Hi @Phil Borrell, Your analysis is correct. If you want to grant selected access to specific projects and not to others, there is no other way than removing any logged in user from the browse project permission in your permission schemes. And obviously that would entail you need to replace that with e.g. a group that holds…

I can only relate to what everyone else here is saying. In exactly the same words as what Matthias has used above, I am honoured to join the group and really looking forward to the experience, in the same spirit of giving back and hoping to contribute in a meaningful way to this ecosystem I am calling home in a way for…

That is correct. This is because otherwise you would lose the context of the underlying stories/tasks in the roadmap. If there are no issues inside your Epics, then the Epic status will be taken into account as well.

Hi @Matt Pippenger, I don't think they are customisable inside the product itself as StatusPage has built-in calculations to roll up impact and component status to the top level. A recommended approach I could find to customise them is through CSS or Javascript snippets. Examples can be found through this support article

Obviously, there's a bit more to workflow design than just the statuses and transitions. Not being sure about your proficiency in the area, this article is a good starting point to learn more about the additional bits and pieces (resolutions, conditions, validators and post functions)

As described in the major incident documentation from the Atlassian ITSM playbook, this is the default process Atlassian describes for managing major incidents: As a process and a workflow are not necessarily the same thing, some steps may be left out of your workflow. That's why you can see how it can basically be reduced…

Hi @Marc-André Lanciault, The filter works on status category rather than individual status. You'll notice that the statuses in your dropdown have colors: * grey representing to do * blue representing in progress * green representing done

Hi @francis.busbus, Welcome to the community. It seems you are on cloud, so in that case, you just start a free trial on the plan of your choice online. You'll be able to choose a url and your environment will be up in running in less than no time. If you've used Jira Server before and would like to migrate your data to…

If the progress bar isn't showing, that is because the start and due dates for those epics are probably not filled out. Have a look at some of the epics that do have a duration on your roadmap so you know which dates fields you need to fill out on the other ones.

It's something I didn't no yet either, but this seems to be related to next-gen indeed. Apparently, history searches are not supported on next-gen. See this related Community thread 

No, just tested in a test instance of my own and it shouldn't make any difference. So I'm guessing it's either something with the transition to status done (it's not because there are items in that column that they changed to the done status in December) or with the combination of your criteria. As @Jack Brickey suggested,…

Hi @Filipe, Have you tried running the filter without the time part in your dates? So like this: project = PDN AND issuetype in (Bug, Spike, Story, Task) AND status changed to Done during ("2020-12-01", "2020-12-31")

Great marketing idea combined with a heart for the good cause. Kudos for this @Inna Gordin! 

Hi @Anish Kumar, Did you make those fields mandatory on the Request form? In your project settings: Request types > select a request type > Request form: That should do the trick. If it doesn't, could you share more information on the steps you took to make those fields mandatory?

Hi @Ghosha, If you are referring to the basic roadmap, your Epics and stories should appear automagically on your project's roadmap if you have it enabled. To read more about that, check out this support article. If you are referring to the advanced roadmap, this is only available on Jira Cloud Premium and not for next-gen…

Hi @Rebecca Kornblum, On Cloud, that won't be a walk in the park, unfortunately. There is a fairly good explanation for this in this support article. On an additional note - and thinking through on your mention of articles - if you are referring to KB articles in Confluence related to a JSM solution, there is a standard…

Hi @Angela Salunga, Yes it does, at least when you are in a space. Maybe you are at the Home page of your Confluence site or the navigation bar may have been collapsed. In the first scenario, navigate to any space or page and you should see the navigation/tree appear on the left hand side. In the second case, either press…

Hi @David Prescott, I think going with classic is going to be your best bet indeed for this scenario. If you really want, you can migrate your imported data from classic to next-gen afterwards if you have good reasons for that. You can find a comparison between both project types from this overview page. Regarding your…

Hi @Lieselotte Dirks, Let me start by welcoming you to the Community and wishing you all the best for the new year! It all depends what you mean by "resource planning". If you think about detailed allocation of work to specific people to assign and forecast workload of individuals, advanced roadmaps is not your best…

Hi @Liu Zhengjun, This can be caused by several things, but potentially a scheduling setting in your Jira instance. Have a look at this troubleshooting article

Hi @[deleted], Yes, that makes sense as releases are specific to a Jira project. As you start your process from the RM project, current project refers to RM which does not have your KEN (or other) releases in them. It doesn't seem as if you can dynamically select projects from the list there so you will have to add…

Hi @Robert Klein, There's a couple of ways to approach this. Assuming your page tree looks like this: Demo Space > Level 1 / page 1 * Page 2 * Page 3 * Page 4 > Level 1 / page 5 * Page 6 * Page 7 If you want a decision report of Level 1 / page 1 and all its child pages, you can configure the macro as follows: Add the macro…

Hi @Jason Gorman, It's important to understand the way product and project/space access work across the different Atlassian products you have on board, look at your current setup and maybe redesign certain things from the ground up. Too many people being granted admin rights is a common mistake unfortunately, but can be…

Hi @Noa Buchman, Assuming you refer to the basic roadmap - not advanced roadmaps of the premium plan - they are a feature you toggle on or off for an entire project. So you can't target specific users to see it or not. Regarding project permissions, check out Project permissions documentation. Mind the difference between…

Done as well.