Comments
-
Have a look at this thread, you can use either the excerpt macro or the include page one to do this.
-
It doesn't matter if you have Atlassian Access or not, the log in screen is the same for every customer and cannot be configured to be specific per customer. We have Atlassian Access to and solves this via SSO, that way only external contractors have to go through start.atlassian.com
-
You have to use https://api.atlassian.com/jsm/insight/workspace/ instead of your instance URL, if you make that change you should get the expected result.
-
You are then looking for a reporting app since Jira doesn't provide something like that out-of-the-box. I bet you can do that in eazyBI.
-
Hi Doug, You can send DMs to specific assignees, but you would have to get their Slack account ID, which is not the same as {{assignee.userID}}. The other option is to send it to a channel and then use @ mention of the assignee, that is how we do it for some of our tickets.
-
Hi @TH, Welcome to Atlassian Community! You could do this by having multiple transitions in the workflow and add a condition on each to check the priority, that way you could use different screens dependent on the transition.
-
Hi @israel siboni, Welcome to Atlassian Community! You can use a filter like the one below to get all issues that were created outside of working hours. There is no option to use businessHours as part of your JQL, so if you would like to see the numbers for the full week you would have to expand the JQL to include each…
-
Yes, so you have to make sure that your workflow has a post function on each transitions that either sets Resolution to none or to the value you want it to have when the issue is resolved. You could also allow the user to set the resolution when moving to a done status, but you would still have to reset it when moving out…
-
Correct, opsbar-sequence only affects the buttons, it has nothing to do with your JQLs. For those you have to use the ORDER BY.
-
See Setting the resolution field for more information.
-
Hi @Adnan Ali, Welcome to Atlassian Community! The strikethrough is based on the resolution field, if that field has a value Jira will interpret the issue as resolved and will then show the strikethrough. So in order to remove it you have to set resolution to none.
-
Correct, you should see three up to two buttons for each transition that is available based on where you are in the workflow, and if you have more than two transitions available you will also see the Workflow button. The order of these buttons are controlled by opsbar-sequence.
-
@Scott McDonald the opsbar-sequence only applies to how the transitions/statuses are ordered under the Workflow buttons, it will not have any affect to filters or views. Your filters and views are ordered based on the ORDER BY.
-
Hi @Sam H, Welcome to Atlassian Community! Instead of using automation to "block" specific emails from creating requests, I would recommend that you take a look at the blocklist feature, which allows you to block specific emails.
-
There are also apps that allows you to share pages externally, like Comala Publishing and Scroll Viewport for Confluence.
-
You can set the order of the transitions by setting the opsbar-sequence. You should consider using values like 0, 10, 20... in order to make it easier to make changes to the order later.
-
Yes, this is possible, you can either use the Excerpt macro or the Include page to do this.
-
Okay, do you happen to use Crowdstrike too? Crowdstrike caused an issue with Jira and Chrome 92, see CLOUD-11248. I would recommend that you upgrade to the latest version of Chrome and see if that helps.
-
Hi @[deleted], Welcome to Atlassian Community! What browser are you using? Are you using any browser extensions? Have you tried an incognito windows or a different browser?
-
Hi @Tatiana Viana, Welcome to Atlassian Community! If you delete an issue you will also loose the history of it. Instead of deleting an issue, consider creating a status in your workflow that indicated that the issue has been canceled.
-
Yes, from what I saw in the documentation you can set up a mapping for the fields that you want to sync. And yes, the set up is done on the Aha! side.
-
Yes, and no. You can add an attribute for email, but it cannot be linked to the Atlassian account. In that case you would have import your users as objects in Insight, link it to the Atlassian account then then on the asset link the User attribute to the object in Insight.
-
Hi @Amit Singh, Welcome to Atlassian Community! Yes, the description is the perfect place to add that information. The Aha! integration does have a mapping configuration, so you could choose not to sync description over to Aha!.
-
Hi @Shai Aviram, Welcome to Atlassian Community! You may want to contact Atlassian Support about this, sometimes email addresses ends up on Atlassian's suppression list if the email bounces.
-
The HTML macro is disabled by default, but you can always enable it by going to manage apps > system and then search for Confluence HTML Macros. See HTML Macro for more information.
-
Hi @weightech, Welcome to Atlassian Community! Atlassian does have a support team here on the Community and I have asked them to take a look at this for you.
-
Hi @Jack Vejvoda, Welcome to Atlassian Community! No, checkboxes cannot be combined with a cascading field.
-
Are you trying to sum it up for all you issues? Where will you be storing the result? The field you highlighted is not a default Jira field, so use that in you math expression to calculate the sum.
-
You can do this using automation, it has math expressions that you can use.
-
So I am an Apple fan too, ever since I got an Apple MacBook Pro back in 2008 (which my daughter killed by covering up the fan vent holes playing a game...no grudges...). Since my roots are in Sweden, I do love what Volvo is doing when it comes to car safety and going all electric by 2030. Not to mention what Polestar is…