Comments
-
status page has changed - they are investigating
-
Status page has changed - they are investigating
-
Bitteschön :-)
-
order must be the last command in your query. Try it first without the "order by": project = RTD and component = ...
-
Hi Ariane, you can combine different conditions with AND or OR, so your JQL would look like: project = RTD and component = <...> order by rank ASC or if you want to query more than one component: project = RTD and component in (component1, component2, ...) order by rank ASC
-
Hi, not out of the box. We do something similar with the Comala Publishing Plugin . With this plugin, you get a "draft" space (the one you are working in) and a public space. You keep both spaces in sync by publishing your changes from draft space to public space. It works well, but is not for free.
-
In the Jira view, there is an option to show only open subtasks:
-
Why do you want to remove them? Do you want to delete the issues or move them to another parent? In my opinion, issues should not be deleted, when they are done. Close them, so you can always see, who and when someone worked on them.
-
done :-)
-
Hi Selene, if you have an issue with a supported plugin and need a fast solution, please call the support of the plugin vendor directly (https://stiltsoft.com/support.html). This platform here is community based. We do as much as we can, but we don't have always the time for rapid solutions beneath our main jobs. ;-)
-
Hi Robert, as I can see in your screenshot, you use the cloud version of Jira. There, you can't see a version, because you can't install any version. There is no version tag on cloud, it is always the latest version, that Atlassian released for cloud.
-
Hi Andreas, we had a similar problem with Jira macros in Confluence and JQL containing German special characters. Maybe it's the same problem on your side. The problem were two wrong system properties on the Confluence side: <sun.jnu.encoding>ANSI_X3.4-1968</sun.jnu.encoding> <file.encoding>ANSI_X3.4-1968</file.encoding>…
-
Hi David, you're right. You can't remove the resolution field from the views, just hide it in your field configuration. Sorry for the wrong answer, this field always confuses me. I tried a little bit with the resolution field in our testing environment and it seems that, when the resolution field is hidden, then new issues…
-
you have to edit your subtask's workflow. Check the transitions where you set a resolution and if this is the right transition or not. If you want to see all issues except the closed ones, you should set a resolution if you close the issue, not before.
-
we also have a central Active Directory in our company. In Jira there is a group called "jira-users", in Confluence there is another group "confluence-users" and in bitbucket "Each user given access to a private repository counts to your plan."…
-
Hi Emilio, since you buy license for each of these applications separately, this should be no problem.
-
Hi David, if you hide the resolution field (and you don't set any resolution automatically, if an issue is closed), you will see all your issues quite often in queries that show "all open issues". Jira treats issues without resolution as open issues, regardless of any workflow state. If you want to hide the resolution…
-
Hi, "Show open" lists all subtasks that do not have a resolution yet. The filter is not depending on any workflow state, but on the resolution. If your issues in state "InProgress" are not shown, then they likely have a resolution (although they are not closed).
-
you're welcome :-) Do you know the search function on the Jira Admin views: It's a great function to search for something that "I know it must be here but I don't know where". Type "Anhänge" or "Attachments" there (depending on the language) and Jira will show you the right page.
-
I'm not sure, whether your question header or question text is, what you meant to ask. They do not really fit together ;-)
-
Hi Lars, you can change the maximum size in Jira on this page: http://<your-jira-url>/secure/admin/ViewAttachmentSettings.jspa
-
have a look at status.atlassian.com
-
Hi Muhammad, it is fixed in Version 7.2.7 as you can see in the ticket. You are on 7.2.6
-
There is also a status page from Atlassian: http://status.atlassian.com/
-
Investigating - Confluence.atlassian.com is experiencing peculiar behavior resulting in degraded service for most users. We are looking into the issue and will update when we have more information. (status.atlassian.com)
-
Investigating - Confluence.atlassian.com is experiencing peculiar behavior resulting in degraded service for most users. We are looking into the issue and will update when we have more information. (status.atlassian.com)
-
Hi Dan, I'm not sure what your question is about. Each attached file, regardless of its file type, is versioned. If you upload a file with the same file name again, you end up with a new version and older versions, which you can also look at in the attachments view.
-
This question was asked twice. Please post your answers here: https://community.atlassian.com/t5/Bitbucket-discussions/npm-command-not-found/td-p/603706
-
Maybe it was closed without setting a resolution.
-
Hi Nicolas, are you sure, that the second issue has a resolution set?