Comments
-
Ok, that suggests a failure on the back-end. Could you read the application log for errors occuring at the time you try a delete? There should be something in <confluence home>/log/atlassian-confluence.log (but check other logs in that directory for errors too)
-
Does your user have the right to see the issue? * Check the permission scheme gives them "browse issue" in the project * Check they are included in the default security level in the "issue security scheme" (note that this is often blank, which means only the permission scheme matters) If you are creating the issue from a…
-
Not directly. You have to create a new classic project then move all the issues from the Next-gen project into it.
-
Effectively, scripted fields run their code every time an issue is indexed. If you write efficient code that does not try to do too much, you will not notice custom scripted fields being used. If your code is poorly written or tries to do a huge amount, you will see a drag on performance during indexing (and this can be…
-
Could you tell us what exactly is wrong? (The video doesn't work)
-
My best guess is that "clarity ID" is a custom field added by one of your administrators in order to record a link to a Clarity item. To "find" it, look at an issue. Or try the JQL in the advanced search "Clarity ID" is not empty To "find" the field itself, look at Admin -> Issues -> Custom fields.
-
Use the REST API to read the issues with that JQL, and limit the response to the two fields you need. Have a look at https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/ and check out the bits about "jql" and "&fields="
-
Just to be clear on the boards, resolution is the measure plain Jira uses for "issue needs no more work". Boards define "issue is in the last right-hand column on the board" as "done" You can set up different boards to map different status to their "done" columns to get different measures of burn down.
-
The summary for an issue is not a calculated field. Could you explain what field you think is calculated?
-
The issue type remains the structural point you hang the configuration off, so no, no change.
-
It's part of the installation, so if you've installed Jira, you have it.
-
You don't. This post is 5 years old so a little out of date, and the App is for Server only as well.
-
Any changes to an issue will be shown on a board that shows that issue. In the scenario you give, your story would show as being in sprint1, on both board1 and board2.
-
You would probably want to clone the issue, then use "convert to sub-task". There are a couple of add-ons around that can do this in one action, take a look in the marketplace for them.
-
What do you mean be "equals to parent"? What is the equivalence supposed to be?
-
This isn't really an Atlassian question, it's about networking. Either your external DNS has lapsed or been changed so your url is no longer available, or your network is no longer routing requests to that url to the servers you want it to land on. Either way, talk to your network team.
-
I suspect your project is a Next-gen one, which don't have permission schemes.
-
Yes, you should be on a supported licence to upgrade to 7.13 However, you could do it with a temporary evaluation licence if you're willing to jump through some extra hoops with licencing it - as you're migrating to Cloud where you'll be paying repeatedly, I don't think Atlassian will mind this.
-
This is the worst possible way to get data out of Jira. Jiraissue is a table containing issues. You need to join it to the project table, then a pile of tables that relate to understanding the system fields attached to an issue, then at least 2 (and potentially hundreds) more joins to understand each custom field. Where…
-
You have made the field required in a "field configuration scheme" that applies to several projects - both the one you intended to and the one where the error occurs. Your field IS "related" to the project because you've configured it to be mandatory in the other project.
-
You will need to feed the results of your regular query through something that issues REST calls to Jira to create the issues or requests in Jira. Do not even think about writing to a Jira database directly - you will destroy your system beyond repair almost instantly.
-
Nope, that was not what you asked for. The answer remains the same though - Cloud rolls on, it does not end-of-life anything, just changes in features.
-
Unfortunately, your experience is simply the opposite of mine. I've worked with companies that simply don't use EWS because it is not secure. Of course, I'm not able to go into detail. The best I can do to help you is strongly recommend the use of secure, open, non-proprietary protocols (possibly over EWS if you don't then…
-
There is no "end of life" for Cloud. Atlassian upgrade every instance every few weeks, so it never goes to "end of life"
-
I think you're missing my point. The subject of the email contains everything you say you need (apart from the body of the comment). For some reason, you have chosen to remove the "this is a comment" part of that subject. Your best option is to put that back, and look at it in Cherwell, like you are for [Jira] and the…
-
Ah, so most of the information you need is still in the subject, but you've removed the "issue commented". Why don't you put that back? As I've said, it looks a bit silly to have: * <someone> commented at * This is a comment * Some information in Jira, when you could parse it out of the subject (if you hadn't removed it)…
-
The summary that is the subject of the email. By default, this will be a Jira prefix, the issue key and the summary - i.e. the information you're asking for. It sounds like you have removed it pointlessly, as you can actually use it. Parsing the default summary is a far better option that adding totally redundant…
-
Yes, that's pretty much the best way to work with Jira here.
-
You won't be able to migrate to Cloud from that version - you'll need to upgrade and then migrate - see https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html You'll find the "integration" with MS Teams and Subversion quite a bit more limited in Cloud though.
-
So why don't you read the summary? Why are you stripping out the data you actually want to work with?