DPKJ Community Champion

I think this is permission issue. I am site-admin on my account. I suggest you use all field export if this is available on your screen. This will solve your problem.

@siddheshAs per information mentioned on change history page - https://bitbucket.org/farmas/atlassian.net-sdk/wiki/Change%20History I can see that support for REST was added in 4.0.0 but later in version 4.5.0 more support was added. But I doubt that in this version they defaulted from SOAP to REST. You can confirm this by…

Based on your screen, @Estelle Adam Please reply in this tread only, it will easier for someone looking for same solution to understand.

@Estelle AdamI have added screenshots for help above.

I am adding screenshots for better understanding, this is deep. Step 1, Click Search Button, a slider from left will open Step 2, Click Advance Search for issues button, in slider and search screen will appear. Step 3, Search for issue based on project or any other criteria, and click on export icon (up-arrow in square…

To export the issues to a CSV, you can perform the steps below: - Click to search for issues > View all issues - Type in the filter what issues you would like to return and, using the detail view, select the columns (fields) you would like to return in the export - Click on the download icon > Export Excel CSV

@siddheshOn external interfaces Jira 6 used to have SOAP endpoints which were removed in Jira 7 in favor of REST endpoints. You need to confirm that your DLL version have REST support. Otherwise as mentioned on this SDK wiki page ( https://bitbucket.org/farmas/atlassian.net-sdk/wiki/Home ) you are running very old version…

@Bartłomiej Jańczak _SoftwarePlant_Atlassian currently host all its site at these locations, * The United States (with locations on the east and west coasts) * The European Union (with locations in Dublin and Frankfurt) * Asia-Pacific (with locations in Sydney and Singapore) And as per their documentation they move…

@Ben CudarsI went on to configure fields from this view (this is visible on top-right corner of screen in new view) After adding field from that config, I have empty label field available as follow on issue right context.

@Sneha A Shave you tried this with API v3. Mentioned here - https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-issue-issueIdOrKey-put

@Jodi LeBlancsuper awesome.

Jira provide you with Notification Scheme to handle events. You can modify your existing notification scheme and add project lead to recipient list for issue update event or custom event during workflow transition. You can go through this article provided by Atlassian to understand notification scheme better -…

@Beat MathysI don't think modifying record directly in backup is correct way to solve this problem. Atlassian itself recommend bulk user related changes using Bob Swifts Command Line plugin for Jira. * Article Link -…

@SandeepJira by default provide CSV export, which you can import into your Excel tool and create reports that you desire. Here is a great documentation - https://deviniti.com/atlassian/how-to-export-jira-issues-to-excel/ Jira also have various reporting plugins that you can browse on Marketplace - Search Marketplace

@Fahad Siddiquifor sure this is valid.

Finally, we have gathered all the amenities.

@CharlieFork is not standard Git or Command Line operation, so in simple words no you can't fork any repository using terminal. But, once you have forked a repository, or you have cloned it in your local you can run git workflow using command line. You can read this guide to maintain sync with upstream after fork using…

Surely the Moon is made for that ;-)

If repository of your professor is public and is openly available, you can clone it. To learn more about cloning a repository read here - https://confluence.atlassian.com/bitbucket/clone-a-repository-223217891.html

@Marco BohmbachYou don't activate there options. They are always enabled, and appear differently depending upon your editing experience, Old Experience New Experience

I think what you are looking for is Label Type Custom Field. You will not need any plugin for this. So, in Label Type Custom Field, you won't set any value initially, but once some one create new label, it will be available for others to use.

You need to create separate user groups for users of each company, and then grant permissions to access project (Browse Project) only to respective group. You can learn more about permissions in Jira here, https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html

@gustavogmatroni You have two solutions, * Ask team member who is account admin to add your new email to team. And later ask Atlassian to merge accounts. * Or just contact with Atlassian as soon as possible, and explain situation to them. - https://www.atlassian.com/company/contact

Too much cheese.

I am on 6.15.x Try this URL directly if this helps, <CONFLUENCE_BASEURL>/admin/pluginusage.action Otherwise, I think you need to look log files if you are getting some error.

@Andy - PTC Redundantdraw me as Kungfu Panda. You won't find me anywhere. I have almost zero social presence :-(

@Niels Molmanshave you tried adding 'comment' to 'fields' parameter. This will give you comments in search api. https://docs.atlassian.com/software/jira/docs/api/REST/8.2.2/#api/2/search-search

What version of Confluence are you on? Have you tried re-login etc, usually this page should appear.

Sneaking a bottle is most acceptable thing, in fact this should a be rule in Moon travel handbook. :-)

@Niels Molmanssearch will not require you to make 22000 calls for 22000 issues. It will be 22000/max_per_search which is usually set to 1000, so 22000/1000. If you are looking for ways other then REST api, * You can SQL Database, there will 'jiraissue' table that contain basic issue data, * You can do that using Java API,…