Comments
-
Hi @Jordan Gower, Welcome to Atlassian Community! The short answer is no, you cannot upgrade a subset of your users to a different plan. If you upgrade it applies to all licenses of the product.
-
There is currently and active incident that is affecting automations, you learn more about it by going to https://status.atlassian.com/.
-
You can have multiple forms on a work item. Do you have a reference that says that this is not possible? You would need to use an app if you want to use custom fields to display information on the portal as other people have suggested.
-
Yes, that is possible and you can use a scheduled automation to do this. If you look in the Template section of Automation you will see a couple of scheduled automations that you can use as a starting point. The rule should be fairly simple depending on what you want it to send.
-
Here is a KB for how to link work items, but basically you just go into one of the items you want to link and click +Add and select Linked work item and you will see something like this: Just select the link type and then in the Search for work items enter the work item key or search on the summary.
-
With the default gadgets this is hard to do. You could use the Average Age Chart, but that would mean that you have to have one for each assignee and a filter for each one. If you have access to Analytics you could create a dashboard there to show this data. Another option is JavaScript Chart From Atlassian Labs, just note…
-
Yes, that is possible and the way do it is to use the Link Work item feature. You use the out-of-the-box link types or create your own. Note that if you want to create your own you need Jira admin permissions.
-
If you do not have access to Project settings then you need to contact your project admin and they can set up an automation for you or give you access so you can do it.
-
Hi @Stefanie Talac, Welcome to Atlassian Community! This can easily be done using automation. You could create a scheduled automation that creates the tasks for you. If you go to the automation templates there is one called "Schedule a recurring ticket" that you can use as a start.
-
It can be done with Rovo, that is free if you are on the premium plan or higher (I think they mentioned that it will be free for standard too during the key note at Team 25, but my memory could be wrong so don't take my word for it). There is an agent in the Rovo use cases and prompt library that can be used to create the…
-
Correct, approvals are a Jira Service Management feature only. For Jira you would have to either use an app or use the workflow workaround I described in the article.
-
Hi @Peter Saulesleja, It sounds like you might be using a team-managed project instead of a company-managed one. If you go into the project it should say what type it is if you look on the left-hand side if you are still using the old UI. In the new UI you have to go to View all projects in order to see what type the…
-
Yes, you can change that icon. Just go into Space settings and under space details you can either upload your own icon or use one from the gallery.
-
Approvals is only available in JSM projects on DC. You could work around it by using circular transitions and automations, I wrote about it in this article. My solution was done in a Cloud environment, but you can recreate the same thing on DC.
-
Hi @Ghata Singhal, You can do this if you store the data in Assets, (if you upgrade to premium plan). If you do then you can use filter issue scope in the child level fields, you can learn more about it in this article.
-
Hi @V_ Menezes, Welcome to Atlassian Community! The short answer is currently no, you cannot be billed for a lesser number of users then than the number of Jira licenses. You can check the FAQ on the Marketplace listing for Zephyr under "How do I determine my cloud pricing?". This pricing applies to all apps.
-
AT the moment I cannot find the documentation, but I just checked my work profile and it does not allow me to set the email to be private, it only allow me to set it to "Only you and admins", and we are using Okta for SSO.
-
The way I solved it at my previous job was to add a form that was linked to the massage field that we wanted the user to see from the portal. The reason we used a form is because you are limited to what Jira fields you can display, and they will be hidden at the top after the request is submitted so the user would have to…
-
The visibility also depends on if you are using and IDP or not. If you are using an IDP you cannot set the email address to private, admins also need access to it since the email address is used for product access and services.
-
Email addresses should be available if you use the Get user endpoint. The response has the email address, display name and other information.
-
Good question, and I don't have an answer on that because I haven't tried it out yet. I would suggest that you go to this article that announced the support for cascading fields and ask there, and then if you get an answer add it here.
-
Hi @Cicely Merrell, Welcome to Atlassian Community! If you are on the free plan the KBs and Atlassian Community is the only way to get support with your products. In order to be able to contact support via the support site you need to be on a Standard plan or higher, as outlined in this KB, Explore Jira Cloud plans.
-
Here is the link to global permissions, https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/. Having Browse users and groups allows you to select users and groups from user picker fields and be able to share work items. And if you have this permission you can see the name of users and…
-
You can enable the Epic panel if you go to the Backlog view and click on the down carrot next to Epic at the top, there you should see a slider to enable the epic panel.
-
Also note that the Hide is currently a cookie setting, so if you need to reset your browser cookies you would have to repeat the step of hiding Tempo again.
-
Hi @Laurent Payette, Welcome to Atlassian Community! I would contact Tempo regarding this, I know there is a feature request for it because we have requested the same thing. Currently you can only hide it per user, if you hover over Tempo the Hide button should appear.
-
Hi @Khuong Nguyen Welcome to Atlassian Community! If your automation triggers on Forms submitted you can use {{forms}} to get the field values. Please have a look at this KB for more information. If your automation is triggering on something else you would have to use the REST API to get the form answers, and it complicate…
-
Hi @Jérémy Macouin Welcome to Atlassian Community! Atlassian support that is on here has been notified and will get back to you within 2 business days regarding this.
-
The reason why you have a big gap between the guideline and the remaining values is that remaining values are not decreased until the work item reaches the far most column on your board. That column tells Jira that the work item is considered done.
-
Without an app your only option would be to create a template with variables for each dropdown you need. Something like this: