Comments
-
What do you mean by "app" here? Client of some form for mobile devices? Server? Something else?
-
It would probably be a lot better to do this with Active Objects rather than write your own data store. See https://developer.atlassian.com/docs/atlassian-platform-common-components/active-objects
-
No, it's not possible, you have to go into the issues to edit them.
-
Ok, use updated instead of created. But, think carefully, as you probably don't mean just "updated", you might want to think about "fixversion was changed to" type clauses.
-
So when you said "The import process was successful" in your original question, that was totally wrong. That error is quite common when using certain databases and trying to move to others, and there's a standard fix for most cases. Have a look at…
-
This is something I would want to question quite a lot. Three reasons If you are embedding a database driver into an add-on, that makes it useless for other databases, and makes your macro useless for other Confluences. Reading an Atlassian database directly is almost always the worst possible way to work with a system.…
-
I'm afraid the filter I gave you works perfectly for me, it tells me the issues that were created in the previous hour that match the project and version.There is no comparison function in JIRA, a filter simply tells you what matches the search when it is run.To get a list of issues "added" in the last hour,…
-
Ok, you'll need to read your logs to see what it's doing while this "churning" is happening
-
If the import was successful, you have already got "users and related info in the server database to the cloud". I'm not sure what you are looking for here? If you've followed the doc, there's nothing more to do. What appears to have gone wrong that meant you reached for support?
-
That suggests your server or client can't reach the Atlassian site. You can do this manually - in the dialog you've shown, select "I have a key". Then, in a separate tab or window, go to my.atlassian.com, log in and select "create evaluation licence". You'll be given a key that you can paste into Confluence.
-
Tell them they're wrong. You have the support of all of us who've looked at the database!
-
It's the same answer, but I can see why my answer is not clear. I'll try to phrase it differently: Let's take the query and rewrite it in natural English: status was Reopened AFTER startOfDay(-1) becomes Tell me all the issues where the status was Reopened after the start of yesterday Read carefully - it's not about the…
-
What "does not work"? Adding the "created >-1h" means "created in the last hour". What you're asking for is your filter plus that. Have I misunderstood what you are looking for?
-
The first clause "status was reopened" means what it says - the status was that at the time defined by the "after" clause. An issue could have gone into that status at any time.
-
6.0 from memory.
-
Start at https://productsupport.adaptavist.com/servicedesk/customer/user/login?destination=portals
-
Ok, good set of checks. The next one is to see if the attachments "field" is on the edit screens for both projects?
-
No, there's no default setup (except in the code, which you can't touch in Cloud)
-
Does the user have "attach file" permission in the project?
-
I'd do it with either one of the "search and replace" add-ons, or Script Runner for Confluence.
-
Depends on how you want when you say "visibility". If the issues should be completely hidden from users while in certain states, then you have a couple of options. One is to use "issue security", setting and changing an issue's "security level" as the status changes. This can be a bit of a pain because you have to get the…
-
Ah, yes, that's the bug. Couldn't find it earlier. It's not happening on my local one, so I can't replicate it, but the bug does say it's intermittent.
-
No, that's a broken idea. The only way you could do it in JIRA is to change the issue type at the end of the first phase, which is a non-trivial act involving data validation and migration. Or, you could close the issue at the end of phase 1 and have some code create a new issue of a different type with the other half of…
-
This doesn't sound like a "known issue" I can find, and changing the names of issue types worked fine for me on JIRA 7.2. I suspect there's something interfering with the edits - could you have a look at the log files to see if there are errors happening around the time you are making the edits?
-
What do you mean by "return nulls"?
-
Go to an issue, and click "link" - you'll be able to link to another issue, or to a url! Obviously, your storage will need to expose the files over a url as well.
-
You could write a listener that picks up the cloning/create event, checks for the clone link is in the event and tags something into a field. Or your Tableau connector could look for the link itself?
-
Not in JIRA itself. Think of REST and the UI as presentation layers that look on to the core functions of JIRA. The core functions don't care what route the data comes in by, just that the person doing it has the right permissions. So, as you've already suggested, the method is networking based - stick a firewall in front…
-
Indirectly yes. There is no problem with you uploading a file to a file-store somewhere and then putting a link into a JIRA issue that points to it. You can't do it as an attachment in JIRA though, the attachment "field" there is only for files attached locally.