Marc -Devoteam- Community Champion

As @Pragnesh Patel Mentions, these are options to look into or otherwise you can always see the marketplace for apps that can add this functionality to Jira

Hi @Tapas Banik ID 552064 is not an issueID in Jira, but an another ID, I expect in in Zephyr. Your example shows it already. issueJiraId:"636735" I would reach out to Zephyr support to ask them to be sure.

Hi @Dany Bellacen Looking at the app and its documentation you wil need to add issue types to your project. See: https://itms-documentation.infodation.com/configuration-for-jira-project/ Otherwise contact the vendor and ask them to help out, as this relates to their product.

HI @Andre Stander Welcome to the community. Are you the org admin of your instance, or just a member of an instance? If it's the first and you can't access the instance anymore, you have been removed by another org admin or your instance has been removed due to inactivity (free tier instance, if not used for 2 months).…

Hi Bill, This solution works. I had to think about this myself!!!

Hi @radha_kannan Welcome to the community. As @Vronik mentions, this won't happen without notification from Atlassian and would also mean you haven't logged into the product form over 2 months. But anyway, an email would have been sent to the admin of the cloud instance, regarding this.

Hi @Hajar Shalaby Welcome to the community. You could look at any time tracking app on the marketplace. There are too many to list them all. Depending on other functions you might require based on time tracking, make your choice or try differents ones as a trail. They almost all offer auto time tracking based on workflow…

Hi @Nicolas Grossi Thanks for the suggestion. This Article I have seen and is the basics, if I would implement this I would have to transform my branch from one rule to 5 rules. The form in the request has many options to choose from, so this I wanted to circumvent. Thanks for the reply anyway.

Hi @Bill Sheboy It's in fact the complete rule. The 1st part is the initial rule and the 2nd part is what I added. An I do agree in your thinking that it relates that branched run in parallel and they run asynchronously. I tried to see if anyone had a solution, as I know you can juts create sub tasks one by one in a rule…

H @Prem This I think can't be done, unfortunately. You could reach out to the Atlassian Developer community, to see if they can help you out.

Hi @Prem You could try to add html like this: <a href="mailto:jira@<tenant-name>.atlassian.net?subject=Re: {{issue.key}} Issue&body=Duplicate">Mark as Duplicate</a> This should trigger a mail action tha the client only has to press sent on Have an automation rule on the project if you want to action that comment, let's say…

Hi @Kyoji Ueda Welcome to the community. I quickly glanced add the marketplace app you describe. I do think it's to show RSS feeds for products outside in Confluence, but not showing Confluence information in the feed as well. I suggest you to reach out to the marketplace partner (vendor/developer) to have this checked.

Hi @anu.m No, that is not possible. First thing, branches on one-and-only-one issue (e.g., branch on parent) get run in-line, as if there was no branch. Branches which could be on multiple issues/things (e.g., JQL, linked issues, etc.) are run asynchronously and in parallel. There is no guarantee when the branch will end…

Hi @Sagi Gueta Adjust the workflows related to the issue types used in the project. Add a post function when is changes to a certain status the assignee is sst based on the actor of executing the transition. This wil only work if issues that are added to a sprint also change status. It has it's caviats, jusr as the…

Hi @Archit dubey Welcome to the community. Looking at the options you are showing, you are on Jira Data Center/Server and are using Zephyr Squad Look at the documentation of the app, how to import. * Zephyr Squad - Data Center/Server

Hi @Marko Blagus No this can't be done. Favouriting Dashboard, Filters, etc are user based options and can only be doen by a user. This can't be managed.

Hi @Ravi Prasad To simply answer you question, No. This can only be done with company managed projects. With team managed projects there are no Issue Type fields, Screens or any other types of Schemes.

Hi @Ravi Prasad Request Type fields don't exist. Request Types are build out of system fields or custom fields in the system and the fields have to be present on the create screen you are using, linked to the issue type.

Hi @Marcel Kaiser To check, are you also a Jira Administrator or just the Org Admin? You do require to be Jira Administrator.

Hi @Marcin Figiel Welcome to the community. As mentioned by @Ste Wright , you need to have a column in the cvs where you present the issue key of existing issues. On importing the existing issues will then be updated with the provided details in the csv.

Are all related tasks in the same project or are they in other projects. If they are in other projects, does the rule actor have the correct permissions in those projects?

Hi @Дар_я Малярик Could you share the configuration of your rule(s), this would definitely help us members on the community to help you in hopefully providing a solution Tnx.

Hi @Ander Baher Project Ops Which gadgets are you using, not all gadgets can display any value used within Jira

Hi @Ander Baher Project Ops Welcome to the community. Indexing is done automatically on Cloud, this is way there is no manual option like on server or DC

Hi @Mitch Cheung Welcome to the community. As mentioned by John, these can't be changed, you can add extra quick filters.

Hi @David Alvarez Alvarez You would need to differentiate the request like based upon a component or label.

Hi @Sushant Koshy Is there any ETA on delivery of this functionality within the global realm?

Hi @David Alvarez Alvarez Create automation rules that for each issue type set a security level and add the relevant groups/roles to that security level.

Hi @Jochen Betz Do notice that "forms" is still not fully integrated in Jira. As this functionality has been implemented by acquiring a former marketplace app. This will take time, automation took more then 2 years to get integrated fully, after the app was acquired. 

Hi @Jochen Betz The "Request Form" field location can't be changed. Simply said it's actually no a field but an option where attached forms are shown.