Comments
-
You will not loose anything - the new workflow does not remove anything and it does not apply to any issues until you say it will.
-
So, as you say it is behaving as documented, I'm not sure where the problem is?
-
A 502 really does mean that either the server can't handle what you are doing, or the network you are on cannot carry it. It is not Bitbucket that is failing, it is your network. You are going to need to read the bitbucket and server logs to find out what is going wrong.
-
The problem is that you're not giving it a valid user for the project lead.
-
So "Ing" is not the username, or if it is, it's someone who can't be set as a project lead.
-
45k issues in a dump file is not in the slightest bit useful for "tracking". As an issue tracker, Jira is far better at tracking your issues. Could you explain what you're trying to "track"?
-
I'm sorry, I was not clear there. What use is this single dump file? What are you using it for?
-
Ok, you can't download more than 1000 issues in Jira unless you edit a properties file to override the limit. Even if you do that, 45k is not going to happen - the limit is there to stop people overloading your system, and that only takes a few thousand issues in an export. Exporting 45k issues sounds totally wrong though…
-
You need to give the lead as a user id, not an email address
-
This usually means that there is something on your network blocking access, or that the server is not working at all. Could you give us more of the error message?
-
But what are they? How are they represented? Are they potatoes? Buttons? Kittens? What is the actual object that is a "test case"? And is it provided by an App?
-
Don't. You should never put credentials in a place that might be shared or become public.
-
Nope, that's what it is supposed to do, and what is documented.
-
Repeating your question does not answer ours. Please read the answer again, and give us the information we need.
-
When this question was asked, almost 5 years ago, you could import the created date. Now, you can not, it really does reflect the date and time you created the issue.
-
Do not delete the index files - they are there for good reasons. One of them is generating reports like the burndown chart.
-
For in-person training, you'll need to get a solution partner in - see https://partnerdirectory.atlassian.com/
-
Your code is feeding your Jira instance a field that does not exist. Try not sending that pointlessly, it should work fine then.
-
And the other question?
-
We can't help you - you are using acronyms and words that are total nonsense, so we can't begin to understand what you're asking. * What is sdms? * What is tp? * What are you registering? * What is a centre tp creation? * What is nsdc? * What is tp under state tp? * Which Atlassian application are you using?
-
"Watcher" is a flag on an issue saying "this person is interested", it's not a user "role" you can attach permissions to.
-
"i updated my jira yesterday to the latest version" - that answers the question because it tells us you must be using Server Jira. Which does not have Next-gen projects or roadmaps.
-
So you are creating issues, but you don't see them after creating them. Is that right? Can you tell us the error you see when you try to look at one of these issues?
-
I'm afraid this tells us nothing beyond the fact you can't see something you think you should see. Please, more information?
-
"trying to call" does not tell us anything about what you are doing. There's no language, no code, no error message, nothing. Please, explain what you're doing and what actually goes wrong with it.
-
Are your administrators explicitly given "browse project" rights via their group or role?
-
No, that's not one table, you need at least three joins for those from just the plain issue data. Seriously, go do this with REST, it's safer, faster, better and most importantly, easier.
-
How are your test cases represented? What do you mean by "pull"?
-
You will need the multi-level cascading select if you want more than the two layers the cascading select does. You could also do it with Behaviours in the Scriptrunner app and several independent fields, but although I like SR, this is something I'd still look at the MLCS for, as it's a lot easier!
-
Have a look at the request type to issue type mapping, so you know what issue type the request is tied to. Now look at that issue type - you will find the field that you're trying to edit does not exist for that issue type, either because of context or field configuration. You'll need to get it re-added to that issue type.