Marc -Devoteam- Community Champion

Hi @Sam Hepworth Welcome to the community. I'm not sure but can you try to replace "remove" with "del"

Hi @Aiden Wishart Welcome to the community. I assume you are able to log time on other issues, so you are in Tempo and part of a Tempo team. The Tempo team you are member might not have been associated with the Jira project DESIGN Are you a Tempo admin in Jira, than you can view your Tempo team and the projects associated…

Hi @[deleted] You are right. @Mikael Sandberg You are right as well forgot that you can change the display options on the project export only with the fields available on the project.

Hi @Frédéric Boisvert Welcome to the community.. No this is only feasible you can roll-up by estimation and dates. Not combined and not by dependency.

Hi @Anneliese Pretorius Do you miss the cog wheel within a product? If so then you are not a product admin, if related to Confluence or you are not in the admin group of a product. If you require more help, please share a screen shot of your user.

Hi @Dhanyasri This could be a solution You would need to create 2 number fields. Create an automation that updates the number field, or decreases the number field on changing the custom field with the option values. You could then the you should be able to have an automation the for an epic compares the number fields and…

Hi @shivani shirguppi You need to create a different context in your custom field. Context are the option to use the same field but with different options. How to add a context to a custom field

Hi @Christopher St_ John I would reach out to eazyBI directly for help on the configuration. They should have had this question before. I would ask them if they are able to update their documentation on the topic as well if its not in there or not in a logic location

Hi @Linda Korpås Change the issue type scheme of this project and add the issue type Epic.

@Martin B Are you Initiative linked to Epic via an Issue link? I think so as you are on a free Cloud plan and you can't have a hierarchy. To achieve you request, you would need an app. You could try Swanly portfolio roadmaps

HI @Martin B What If you use Epic Link. Parent and Parent Link are fields related to Advanced roadmap, as you don't use this you could try to use Epic Link

Hi @Sheri Widler The is currently no option to do this. There is an open request for this at Atlassian https://jira.atlassian.com/browse/JSWCLOUD-20382 

Hi @Christopher St_ John I think your question relates to SSL setup for EazyBI this can be found in their documentation https://docs.eazybi.com/eazybi/set-up-and-administer/private-eazybi/https-or-ssl-setup 

Hi @Roland Uittenbogaard This is not possible. The System default Field Configuration Scheme isn't changeable, it holds the Default Field Configuration by default You need to create a new Field Configuration Scheme and associate your new Field Configuration. Then Change the Field Configuration Scheme on your project.

Hi @Guido Burckart Welcome to the community. That's seems strange to me when shortening the email address the invite is received. I would suggest to raise this as an issue at Atlassian Support. This could be a bug, or the should mention a limitation on email length (my opinion)

Hi @Simona Cristaldi What is the configuration of your SLA's? But based on your explanation, SLA's don't recalculate, they depend on the config. Your Time to First Response it set to 2 hours, this means you have 2 hours to comply to the SLA. If you are over the 2 hours you are breaching your SLA. Your Time to Resolution is…

Hi @craig_ross Welcome to the community. Yes it can, see the Atlassian documentation. Receive Requests From Email Integrate Jira Cloud and Slack Chat Slack and/or Teams Create Issues In Slack I hope these links will get you the answer and to help you in your decision.

Hi @Zaldy Parian A got option for this is an app from Caelor, I have used this as well. custom-field-suite-powerful-custom-fields-for-jira-free Here you are able to create multi level cascading fields an loads more.

Hi @Sandra Henriksson Can you check the URL that your are using. It seems that the URL you are using is pointing to a specific issue, the issue key is present at the end of the URL. The message presented is an indication that this specific issue has been deleted from the system.

Hi @Ujjawal Raj ServiceNow has spokes in there store to connect to Jira. I think these might give you the guidelines to simply connect SN to Jira in your case. Here is the link:…

Hi @Sari Kachorovsky I see you team field has the ID: customfield_12300 from your original post and there is an error in the json You missed the closing quote " after "{{team}} I think your json should look like this: { "fields": { "customfield_12300": "{{team}}" } }

Hi @Sugriv Yadav Create a new screen with only the required fields that can be changed in the transition Edit your workflow Create a new transition to itself. (use the old workflow editor) From is from Any state and To is to itself, this will create a loop transition, and set the created screen off-course When the…

Hi @Sari Kachorovsky You are missing a } at creating the variable. The right input is: {{issue.customfield_10001.id}} Make sure that the Team field in you instance has the id 10001. I think it will as I think this is the default id value for field team.

Hi @Priyanka Gupta Are you on Cloud or Server/Data Center? This question is here a I know that using the /rest/raven option in your URL to call the API is a Server/DC option and not cloud And in Cloud this is not an API action that can be achieved. There is no option for associating existing Tests to a Test set via the API

Hi @Faizal Ahamed What if you remove the labels and status, so start from basics. JQL: project = IOA and type = Bug ann updated >= '2023-08-14 16:20' and updated <= '2023-08-14 20:00' Do you get search results? If you do add and status = reopen etc..

Hi @Collista Lewingdon The Team field is not available in the field dropdown in automations even if available in your project. This is a know topic, the same applies to Epic Status. These fields can only be addressed via a JSON statement in using more options in an automation. 

Hi @Priyanka Gupta What Test app are you using in Jira? This will help members of the community to help you out, as currently we don't know what app is used for testing.

Hi @David Tieman In the clone issue action make sure to add the linked issues field to be set. Example:

Hi @Tom Stevenson Yes indeed you need to look what the payload is providing to use the information to create a Jira issue

Hi @Sari Kachorovsky This will do the trick I think. * Before creating an issue add the action: Re-fetch issue data * Then add the action: Create Variable * Then create the issue and use the json