Walter Buggenhout Community Champion

Hi @Vishnu Vardhan Chenna, If the parent you are setting with this rule is correct, the copy the reporter from trigger issue instead of parent issue. Hope this helps! 

Hi @Trudy P Claspill, Maybe this Community article on searching for an exact phrase may be relevant. It is not an exact match with the behaviour you describe, but I can imagine the changes they made impact your scenario as well. 

Hi @Trudy P Claspill, Although I have done quite a few migrations to cloud, I must say I haven't paid attention to columns in the past. It has been the case that many filters (if they were cross-project) didn't even migrate at all in the past, so we were usually happy in many cases with the filters themselves just being…

Hi @허가영(한샘몰PM1팀) and welcome to the Community! If your question is about Jira Software, then I must share the sad news that showing sub-tasks on the (basic) timeline is not possible. There is a feature request that you can track here; JSWCLOUD-18677. If you are on a premium plan, than you can use Plans (formerly known as…

There's nothing conclusive on the screenshots, @Lizzeth Campos. The only things I can see, is that this is a custom made sub-task issue type and that it apparently has a lot of fields on it (I notice there are several tabs on the issue create screen). In the first screenshot, you can see the scenario I was describing. The…

Hi @Abhishek, I am not sure if I understand entirely what you are trying to do here. But the combination of Testing required and Tester seems correct. I just think that the additional condition that says "the issue must have been in status In Progress ..." is overruling your other conditions here. Since you are using a…

Hi @Ryan Taylor, No and yes. A user's email address is what identifies that user in the Atlassian ecosystem. So, having 2 different email addresses to represent the same person would force you to have essentially 2 different users in the system. That is technically possible, but most likely not what you want and more…

Hi @Lizzeth Campos and welcome to the Community! I don't see any images attached. But apart from that, the error message you refer to is not very informative indeed. Most commonly, failure to create issues is often linked to required fields not being present where you are trying to create the issue. e.g. when you are…

Hi @Vanessa De Boeck, This is a classic issue; As Atlassian promotes openness by default, permissions to projects follow that logic. And so, in the permission schemes of projects you create from built-in templates, you will see the browse project permission being granted to any logged-in user or something like that. That…

Hi @marshallmm, No, not really. As an alternative, you could reverse the logic and use automation to update the summary of your tasks after they are created. Your automation would look something like this: * Trigger: issue created * Action: Edit issue / update issue summary to {{issue.parent.summary}}: {{issue.summary}}…

True. Having to read through a massive list of comments to get up to speed does not seem very effective either (apart from the translations). In JSM Premium, Atlassian Intelligence already offers the capability to summarize the highlights from all comments on a ticket with a single click. I can imagine this capability to…

Hi @Marc Lehr, If I select any text in a Jira issue or in a Confluence page and right click on it, I can choose to translate that selection into English. That is - afaik - a browser feature in Chrome, that lets you define the available languages as well. Being an application running in the browser, I think leveraging…

What your manager says is just what he/she thinks it is. I would not assume he/she has full knowledge about the way Tempo configuration works. The only conclusion I would draw from that statement is that he/she does not see anything wrong. I am not working for Atlassian, not Tempo and can't access your site, so I can only…

Hi @abeera.iqbal, Tempo uses a weekly or monthly timesheet cycle behind the scenes with corresponding approval. These cycles are called periods. When a period ends, users are expected to submit their timesheet for approval. Both timesheets and periods can be closed, thus locking the hours logged in them. If your timesheet…

Hi @LC, I don't know the size of your organization and I don't know how your teams are organised, of course. But since you ask ... 😉 It is quite common practice to let at least certain teams contribute to your JSM tickets in this way. The most typical scenario is when you have IT support and development teams working…

Hi @ESTERBEN, You can limit who can perform certain actions on issues in a project through the project permissions (assign issues, assignable user, edit issues, ...). And you can restrict bulk editing to specific group of users in your Jira's global permissions > Bulk changes. But a user who has the permission to perform…

Obviously, replace {{issue.xxx}} with triggerIssue, ... according to what you need to send the correct links.

Hi @Amitsinha Patil and welcome to the Community! You are writing Jira syntax in your rule there, while you should use proper html tags in automation. The following should work: Testing has failed for issue <a href="{{issue.url}}">{{issue.key}}</a> Hope this helps!

Hi @ivychan, It seems that your Atlas and Jira are in different sites (i.e. having a different base url, the part before .atlassian.net). And even more so, these different sites appear to be under a different organisation. You will not be able to connect Atlas and Jira if they are not part of the same organization. Hope…

Hi @Anders Hebert, In many cases, projects in Jira are even hard to align with a project in the real world. Think of a project in Atlas as a (business or IT) initiative that you want to report health an progress on at regular intervals. Projects in Jira are basically containers for work, having a common context. That…

Hi @LC, There's 2 ways to do this: via the customer portal (but that would not be very effective if there's a lot of tickets there) or by letting people the tickets internally (e.g. via search, on a dashboard, ...). To make issues viewable via the portal for your entire organization, you would need to set up an…

Hi @Hrithu Olickel and welcome to the Community! There's a couple of things to keep in mind here: * Jira Product Discovery is based on team managed projects, which means its issue types are unique to each project. So indeed, creating same type as the issue can't work since you're trying to create an issue across different…

Hi @Thomas Kerman, Text fields in Jira do not support '=' - it is as simple as that. Expecting users to enter exact text matches in a field up to 255 chars (I am reversing the logic on purpose here) is not a good expectation. If you are certain about the values you expect, it's better to use one of the structured custom…

Hi @Анатолий, Atlassian does support a multi-lingual interface. Even more than 2 languages. Users can select their language in their personal account settings. From the user avatar, select manage account and under account preferences set your preferred language. Across Jira, lots of custom configuration elements can be…

Hi @Rod Halat, Navigate to https://support.atlassian.com/contact/#/ and select Billing, payments and pricing. You will be redirected to a specific portal for billing and payment requests where you should be able to raise your request / concerns. Hope this helps! 

Hi @011_avinash, Toggling the estimation feature on/off does normally indeed add/remove the story points or original estimate field. However, nothing prevents you or another project admin to manually add the same fields to your issue type screens. I have been able to reproduce that scenario myself by disabling the…

Hi @Gareth Gauci and welcome to the Community! The efforts per team are very much part of the implementation process, which is - as you describe - perfectly managed by each team autonomously. And so they are managed in JSW on the implementation issues rather than in JPD. Even when the effort required is different across…

Hi @RASSE Manuel and welcome to the Community! What mails are you talking about? Default notification emails from Jira by default have a link to the issue in them. So, assuming you are referring to emails you send using automation, you can include a link to an issue using smart values: Hope this helps!

Haha, don't be 🤗 - it is not the first time it's been asked and it is a well hidden little thingy ...

Hi @D, Additional hierarchy levels above epics are part of Jira Software's premium plan and require the Plans feature to leverage them. As soon as you're there, the hurdles you refer to will no longer be there. Hope this clarifies!