Marc -Devoteam- Community Champion

Hi @Ramazan Keskin My suggestion would be to create a component in your JSM project. Add the component on any request type you have on your JSM portal, and hide this field on the request types. Hiding will require you to set a default value, set the created component. All issues raised via the portal will now have this…

HI @Sandesh TM You can achieve this by modifying the issue type scheme used in the project. If you use that scheme in multiple projects and you don't want to impact them all, create a new issue type scheme and set the default issue type.

Hi @Md Eashir Arafat Generally, no, it's not legal to do that. It's a breach of your agreement with Atlassian if you use a Cloud product.

Hi Kuthubdeen_FEROZ@ssg.gov.sg Welcome to the community, Yes you have to set the explicit options for Set up an open portal, to allow you portal to be open for anyone. The other access options will not work, if you want to use the JSM widget.

Hi @Steve Suranie I expect you this rule executes on the creation of the issue? Use the Re-fetch issue date action before you if/else statement, this should solve your issue.

Hi @Dorina Tóth Welcome to the community. You have reached the community form where the members are able to help you with questions in relation to Atlassian's products and in cases with marketplace app related topics. You question is related to a specific function the does not exist in an app, we as the community can't…

Hi @Matthias Vogt "Can I define a "standard" for new projects? Or what setting is used, if I create a new project with an exisiting screeen?" No you can't, so the answer is the one you already provided your self -> "Copy issue layout" is the only way to get all projects to the same layout?

Thank you all. And thank you @Monique vdB for the shoot out.

Hi @Filip Baszak I would reach out to Atlassian with this issue that is occurring on your instance They can see logging on their end, on cloud you are not able to see the backend configuration of your instance

Hi Tim, This is behaviour as I expect it to be. The none option is an Atlassian option, but this can't be set as a default, this option disappears as an option if you use a default set option. If you think this should not be the behaviour, I would ask you to raise an issue at Atlassian itself.

Hi @Kehsi Dow Welcome to the community. You have reached the community form where the members are able to help you with questions in relation to Atlassian's products and in cases with marketplace app related topics. You question is related to a specific function the does not exist in an app, we as the community can't tell…

Hi @Matthias Vogt For Company managed projects: go to the layout section in you project settings here you can define where the fields appear in the issue view. For Team managed projects: go to the issues section in you project settings here you can define where the fields appear in the issue view. Check the context field…

Hi @Praveen597 On the JQL you are using on getting xray information, it seems to me you are running Jira Server or DC, as the used JQL option doesn't exist in Cloud. I expect you JQL to look like; issue in testRepositoryFolderTests("POR", 'Folder 1, "true") this should give you all tests within Folder1 and sub folders…

Hi @Shivani Bhardwaj The articles above help to guide you, but simply said; To remove a label, you would need to find all issues using the label to be deleted and bulk update or create an automation (trigger manually or scheduled) to find all issues and remove the label. 

Hi @Valerie Wilson Is the estimation setting in the plan set to hours or days. this should be the case and all issues related to the kanban board should have the team field filled with the value QA If al issues in this project are for QA, you can also create an automation rule that based on issue creation the team field…

Hi @Priyanka Gupta That means that the component field is mandatory on creating an issue in the project where you want to create the test execution issue. You will need to check the configuration of the Jira project. Check the Field Configuration Scheme or Workflow

Hi @Nita Sexton The solution you are able to use is to create a permission scheme where only the browse permission is granted to user who still need to see the project. If you want to hide it for all, just give Jira admins the project admin permission and browse permissions to a project role I would create a new ole in the…

Hi @Ashok Shirppi This could be possible but, this would require a summary attribute on the objectType component in assets For example, if you wanted to only show a list of components owned by the current summary, you could configure the Filter Issue Scope (AQL) field by typing objectType = “Component” AND "Owner" LIKE…

Hi @Valerie Wilson How does you Team configuration look like? How does your plan configuration look like

Hi @Priyanka Gupta What do you currently have in Jira? Do you use the xray issue types Test and test execution? You need to create a test, and a test has test executions. in the test execution the referenced test is set to passed via the API. Based on the field configuration in your project it seems that the component…

Hi @Uri Shavit You can have multiple board on one project yes, if your project is a Company Managed project A board is based on a filter, so based on the filter you can differentiate what you want to see on a board

Hi @Uri Shavit Welcome to the community. You requirement is not possible in a single board on a Jira project A board can have multiple columns, to have column to be visible on a board this needs to contain a workflow status. This can only be done by using different boards on the project, to have a different column layout.…

Hi @Even Dietrich Welcome to the community. If this impacts a single user and you have determined all settings are equal to all other users, I would raise an issue at Atlassian Support. They can see the backend of your cloud instance and see if there is anything related to this user. Or are you using an app on your…

Hi @Zeerak Khurshid As @Joseph Chung Yin mentioned, the application logs should provide more info. Also documentation to setup OIDC can be found here, are all the required steps taken?

HI @Priyanka Gupta Xray provides an API. See the documentation around importing test execution results here

Hi @Aleksandr Ganiyev Archiving issues is not a function in Cloud. You can archive a project. But this will not free storage, as you are able to unarchive projects. Even deleting information from issues will not free up storage. I have encountered this my self when my business was changing the location of our instances.…

Hi @Zacher Viktor Yes you could. Assets is the former app Insight for Jira. It's a CMDB app, so if you create your scheme correctly you are able to setup organisations and services and link services to organisations that use the services. You can find all documentation on assets here if you want to have more context 

Hi @Valerie Wilson You would need to set a team on your plan, by default there is one (empty). This team requires members (members in you project), of the project(s) that are in the plan. You need to configure the capacity of the team, this based on the estimation metric used in the plan and the project The source of the…

Hi @Tiago Pereira What project type are you using Team or Company Managed? If you're working with a Team Managed project. Automation for Jira does not yet support the People field used in Team Managed projects, unfortunately. Listed in multiple change requests in the Atlassian backlog:…

Hi @백재현/DevOps The feature is called assets. All documentation on how to use assets (formally known as Insight), can be found here