Comments
-
There is no "move workflow", there's just a function that allows you to move issues between projects and differently configured issue types. The function does the minimum it needs to - checking for incompatible configurations and either dropping data that can't be held in the target issue, or asking the humans to fill in…
-
Ok, so why did the doc not help? What is the actual problem you have here? What are you trying to do, and why?
-
What are you trying to do that triggers this error?
-
Jira will move open stories to the next sprint when you close the current sprint, without any status change. The story will take its parts with it (sub-tasks are part of a story, not separate items, and hence are "in a sprint" when their parent is) Note that there is a case where Jira will block sprint completion - when…
-
Welcome to the Atlassian Community! Could you explain more about what this has to do with Confluence, please?
-
Yes, this function helps prevent spam. You'll need to post something new, not repeat what you said before (which isn't of any help anyway, we've already seen what you said) Did the doc Fabio referred to help fix your problem?
-
This sounds like your base URL could be set wrong, can you check what that is first? It can be found at Admin -> System -> General configuration Given your URLs above, I suspect you've got it set to https://jira.mydomain.com/undefined and it should be set to https://jira.mydomain.com If it is not that, then you'll need to…
-
You can expose them to unlicenced users, but to do it, you have to make the entire project completely accessible to the entire world (anonymous access). You can still hide other issues in the project by using issue security, but it's easy for us humans to forget to secure every issue that needs it as we create or edit them.
-
I think your issue types are configured to use different workflows. Your REST call is failing to transition the issue after the issue type change because it's trying to use a transition that isn't in the workflow the issue is now using. You'll need to read the workflow it is using to find out which transition it should be…
-
See https://confluence.atlassian.com/adminjiraserver/migrating-jira-applications-to-another-server-938846962.html It's actually surprisingly easy to move a service from one server to another, the main problem is usually just "how do we move a large amount of data from one to the other?"
-
The XML contains all the app settings in it (where they are configured inside Jira's UI), and that should just reappear when you re-enable the app. The apps though are kept in the home directory of the system - a minimal backup of Jira should include the database (either a database dump or the XML you have) and the home…
-
The best option would be to ask your people to stop sending emails with silly pointless formatting in the subject. There's no way for the email handlers to remove the junk from the summary, they're not designed to do any processing of the text that is in the emails they get sent.
-
Sub-tasks can not have sub-tasks, That's why the error message is telling you that you can't create a sub-task under a sub-task, it's not a valid structure.
-
The best thing to do with CVE reports is to subscribe to the updates on the CVE reporting site that you prefer. I think Atlassian are better than most organisations when there is a security problem. (If we go to the extremes, Atlassian announce security issues within weeks, but we're still waiting for MS to announce…
-
Short answer: Yes All the Atlassian tools talk to each other almost automatically, all you have to do is say "hey, application X, application Y is over there" There are some version dependencies - the applications do need to be of versions within similar ranges - there's no point trying to hook up a Jira 3 to a Confluence…
-
Makes sense, but I think education is probably the best approach here - tell your people that the tool is aimed at developers, so it talks a lot about software, but they don't need to worry about it. For them, it's just the most appropriate thing the software does to support them, and that one "field" has not quite the…
-
Welcome to the Community! Trello does not do any "sync", it does not need to because it is a centralised service. Your different devices are not holding any Trello data, they are connecting to and reading the data from a single central service. If your devices are seeing different things, then your devices are caching…
-
You'd need to create and populate a field to hold a copy of the epic link on the sub-tasks.
-
Welcome to the Community! You will need to talk to your admins - one of them has added a post-function, Automation, listener or script which is creating this sub-task, and they're the ones who can remove it.
-
I'm afraid your version of Confluence is too old for export and import, you'll need to upgrade it and export again. You won't have to do a massive upgrade to the latest version if that's a lot of trouble, but I'd recommend getting it up to at least 6.latest. There is another option though - temporarily install a new, empty…
-
Yes, Trello scales fine to thousands of users. Whether it is a good choice is up to whether it does what you need or not, user numbers are not important.
-
Welcome to the Community! In terms of licencing, the concept of a team is an irrelevance. You will have to licence power scripts for the number of users of your Jira, whatever teams are in it and using the app.
-
I cannot replicate this at all. I've got Chrome (no extensions, like you) and have tried it out with my usual Adaptavist dashboards (9 favourites) Tried again on a different machine that was "off the shelf" (Ubuntu 20.04, chrome as built in), it all worked fine. We have to start asking what is different in your systems to…
-
Welcome to the community! I'm afraid that your question does not make a lot of sense. I could take a guess, but I doubt the answer I might give would be what you want. Could you explain a bit more please? You use words such as Empty, Option, and Archive, but do not explain what they may mean to you. What are you trying to…
-
Welcome to the Community! Do not try to do this. At least, not for your people. It's fine if it is an automated report, but you should never denigrate and ignore your humans by destroying what they wrote to summarise their issue. There is nothing wrong with your naming convention, but it should be going into dedicated…
-
The message fields only apply to issues, not the requests that the customers see. Instructional text for customers is something that should be done by the portal, it's not something for the issues behind the requests. (that's my opinion, not a suggestion or even something for Atlassian directly. I've talked about the…
-
Epic Status is a little different to issue status. To complicate things, Epics are really issues with some more functions added to them, and because they are issues, they have a workflow and an issue status. The issue status for an Epic does not have a strong link to the Epic status, Epic status is a simple article that…
-
Welcome to the Community! Start with a look at the space permissions. The "owners" of a space can do this with you (I think the "owner" of a space is "any non-system admin who has admin rights over the space"), as can your system admins. How are you named as a user who can use the space (view), and create/edit pages? Are…
-
I couldn't agree with @Bill Sheboy more! Specifically: * If your engineering team is doing the work, why is that work in other teams' backlogs? A backlog is supposed to be a pile of issues that a single team needs to deal with. A team should never be looking at other teams' backlog for their work. There's nothing wrong…
-
You could also hack the code that displays the issues, adding in the display of the fields you want, but I would not recommend that. Apps are a better option for improving linking functions.