Walter Buggenhout Community Champion

Bonjour @Sandra MATRAT, Quand tu dis que tu transformes un ticket de BPO vers FRIT, j'ai límpression que tu passe le ticket initiel d'un project Jira à un autre. Cela explique le changement du préfix dont tu parles dans ta question. Je peux bien m'imaginer que ton écran se base en effet sur un filtre de tickets qui se rend…

Hi @Kathi Paquet, You are correct. 1 JSM project can have only 1 incoming email address (that's something you could work around by forwarding mail aliases with your mail application) and only 1 request type (that cannot be changed). So, if you need a different mail address to create a different issue type, the easiest way…

Hi @Itamar Zabari, If your question is about Advanced Roadmaps, your question refers to a time when capacity was managed by explicitly adding individuals to your team. That was the case in the Live plans, version, which has been replaced by a new planning interface. Capacity is no longer managed on an individual basis, but…

Hi @William Porcelli, There is no built-in concept in Jira to group organizations. An Organization itself is already a concept that groups customers / reporters. JSM already allows you to set the Organization of a ticket automatically if the reporter belongs to one. So I am quite sure you should be able to: * run…

I am not much of a brand guy myself either. And though it's not going to win me an award for originality on this forum, the only brand I really have a strong affiliation with, must be Atlassian. I guess the main reason is I can relate 1-1 and very strongly with the company values. And the way the company and its people…

Hi @Sami Purho , You run into the issue here that issues without an SLA target essentially don't have an SLA. SLA's are intended to help your tickets prioritise based on the goals you set forward. If you don't have a goal, there is no timer and thus, no value. So if you want to measure lead / cycle times for issues without…

Hi @Jessie Daniel Manansala, That means and your co-admin are currently the only agents in your Service Desk. If you want other people to see the SLA, they need to be agents of JSM too. That is managed in user management / product acces to Jira Service Management. If you grant users product access, they will consume a JSM…

That's awesome! Thanks for that extensive and clear heads-up, @Vahan Alaverdyan. Could you take a second to mark the answer as accepted as well? That makes it easier to find for users with a similar problem! 

Thx for chiming in, @Maciej Dudziak [Deviniti] 

Hi Nita, Although the "#" isn't explicitly mentioned, there is a paragraph on special characters in the article you listed that says: Special characters aren’t stored in the index, which means you can’t search for them. The index only keeps text and numbers, so searching for "\\[Jira Software\\]" and "Jira Software" will…

No problem @BIQ HS, as you can see, your question is still getting noticed 🤗 

Hi @Jimmy Trivedi , What you are trying to do goes against every rule in the book: when you use sprints, the idea is that you very consciously decide which issues are planned in a sprint. So automatically assigning every created issue to the active sprint goes directly against that. If that is what you want, you would be…

Hi @Or ate and welcome to the community, Your user data is private to you, I'm afraid. So I would suggest you start by having a look in Jira itself and investigate: * the permission scheme that you are pulling the data from in Jira and the detailed permissions; * the users assigned to project roles inside the project…

Hi @Sindhu D M , The link @Benjamin shared describes how to set up an email channel for your JSM project. As soon as that is available, that mail address will be parsed automatically by JSM and incoming mails will be parsed. However, when someone sends a random email to that address, a new ticket will be created with the…

Hi @David Meredith, Your question goes a bit beyond a simple question / answer dynamic, I'm afraid. But a good way to look at things is from the angle of planned versus unplanned work. Everything your customers are asking or reporting (incidents, changes, service requests, ...) is - at least initially - unplanned work. It…

Hi @Erica Grant, As far as I know, in team managed projects all statuses must be mapped to a column of your board and the first column of your workflow should be the left-most column on the board. If you activate the backlog feature, you will indeed see the behaviour you describe. The first status of your workflow will be…

Hi @Cristiane Ruedieger, This is usually due to the fact that you don't have the global permission Browse users in Jira. This permission can be granted by a Jira Administrator through Jira Settings > System > Global Permissions. Hope this helps! 

Hi @Juan Portero, Sorry that I reply in English - my Spanish is a bit rusty. You can find the procedure to change the filter owner in this support article. Hope this helps!

I am not entirely sure what you mean with "the second option". If you mean Data Center, the expiry date of your license makes your product read only. You'll need to purchase a new license before you can use the product again. For server products, your license is perpetual. That means you can still use the product and it…

Hi @BIQ HS , From what you describe, it looks as though you have done a migration to cloud. As you mention issues and reporters, this looks like a Jira related question instead of Confluence. I suspect that your users have been migrated, but they don't have product access to Jira yet. To fix that, navigate to your site…

Hi @Casey Whitehead , It looks like there is a problem with an approver for your request. An automated function is trying to select a user that is not / no longer an active user. Have a look at the approval settings for the issue type you are creating or a postfunction of the workflow of that same issue type that tries to…

As for Data Center, that comes bundled with Advanced Roadmaps, which already has a Team concept included. Although it wouldn't hurt to give that a bit more love, there definitely is something of a foundation present there as well.

I think everyone agrees that this is a key thing in planning, tracking, managing and reporting on work for teams inside Jira. Many of the above comments do rightfully point out that this is going to be a challenging endeavour, with many dependencies on existing features across tools and marketplace apps. There's also a lot…

Hi @David and welcome to the community! First of all, it seems you haven't purchased the licenses yourself but rely on someone in your organisation to get you the license keys. Ask that person to check in My Atlassian (that should be the place he/she got the license keys for you) to check if and when the licenses have…

Hi @Mattia and welcome to the community, Yes, this is true. And yes, this is under investigation through this request: JSWCLOUD-17371. You can watch that ticket to stay informed of progress. Be aware that for cross-project collaboration, Jira Software Company Managed projects are perfectly suitable as of today and the…

Hi @Vahan Alaverdyan, It seems rather unlikely that the story points feature disappeared altogether from your instance. At first glance, I would think it is more likely that a configuration glitch somehow made the story points custom field invisible. That may be related to the field configuration scheme of your project or…

Hi @[deleted] and welcome to the Community, I think it may help if you move the post function that sets your resolution below the Create the issue originally post function. As it is now, you are trying to set the resolution for an issue that does not exist yet.

Hi @Theis Joergensen , I reckon you are trying to measure SLA success? You can do that with the available JSM custom reports. You can read more about that in this support article. While the article is about data center, the same principles apply to cloud reports and I believe the article explains better how it works than…

Here's a link to the REST API docs. 

Hi @milind.khanzode and welcome to the community, The WIP limits on a kanban board are not restrictive, so they won't block you from adding items to a column. They will display the background colour of the column in red, so you have a clear visual indication that you have too many items in a column. Suppose that you have a…