Comments
-
Cancel the payments and create a new one.
-
Ok, so you're asking why only some people can edit a field?
-
Tasks appear in the roadmap, and epics too, so we're a bit stuck on the title of your post. In the body "convert my tasks in epic" makes no sense either. Could you explain your problem(s) again please? What do you mean by "convert task in epic"?
-
Nothing, there is no difference. Could you explain what you think might be different within the same system telling you the same thing consistently?
-
Actually they do. But they're still waiting for a useful definition of how to usefully estimate subtasks in a way that works for everyone, fits with all the Agile methodologies and doesn't break all the reporting.
-
A lot of places drop enabler stories into projects they describe as "aspirational" - places where ideas are welcome, but don't directly lead to any code
-
No, you will need to write/script validators that look at the parent issue type and block the sub-task creation if they are of the "wrong" type.
-
You can not do this, as it is nonsense. When you create an issue, it has to know what state to create it in, it makes no sense to say "I create an issue in a state that is totally undefined" But you can have different status by issue type - it does make sense to say "bugs start as 'needs investigation' while new features…
-
You do not put sub-tasks in sprints. They are part of a story, and hence it's nonsense to treat them separately. You put a story into a sprint and all the parts of that story (i.e. sub-tasks) go with it. Jira has a reporting weakness in that it does not show sub-tasks as being in any sprint, but they are in the sprint…
-
Jira has a REST API that you can use to create and update issues with from other systems. Sadly, from my memory of Lotus Notes, it's pretty much useless at integration (alongside being useless in general), and you'll have to do a LOT of coding and hacking to make it do anything useful. Your most simple approach to this…
-
What do the logs say when you add parameters? What else are you adding?
-
Still not clear, but I can make a guess. Do you mean: I want a customer to be able to create an issue, but not edit some of the fields after they created it Is that right?
-
No, if you can see an issue, you can see all of it. In real life, it's a bad idea to hide details from people, because if they can only see part of it, they will ask questions that waste your time.
-
This looks like you've put the right settings into a connector, but the proxy is connecting to another connector. What does your nginx proxy point to?
-
An attachment in Confluence is just a simple blob of data that can be downloaded as a file later. Some of the code in Confluence has been written to read and interpret the content of these blobs - the MS Office macros in particular can reach into an attachment and pull data out to be displayed. There are two things to…
-
No, Atlassian use a "trial" model instead. You're free to download and install Jira and give it a trial licence to try out for 30 days on Server or 7 days on Cloud.
-
Scriptrunner's Behaviours can do this (a little bit of scripting though, but a 3-liner and not that scripty, and part of ScriptRunner rather than something you have to think about on upgrades and moves)
-
What is the board filter? What does it return when run in the issue navigator? Have you drawn loads of issues into the current sprint? Also, it is unclear what the numbers 5 and 220 are - story points? Numbers of issues? Could you explain these?
-
Yes, this is the correct behaviour - it does not make any sense to have an issue on a board twice, it's pointless noisy duplication. Your "all" swimlane is showing you "all cards on the board that have not been grouped up with others".
-
And what has that got to do with verification?
-
I'm afraid the top part of a very generic error is not going to tell us a lot. Please read the rest of the error messages, concentrating on the "caused by" that you've dropped off the end of your screenshot.
-
See https://confluence.atlassian.com/adminjiraserver/migrating-jira-applications-to-another-server-938846962.html
-
Could you try the "Can't access your account" link towards the bottom of the page?
-
>Shall we use Jira crowd Rest-api for jira server? Could you explain that question? I ask because "Jira crowd" makes no sense - do you mean Jira or Crowd's REST API? And why do you want to "use it for Jira server"? What does that mean?
-
Yes, you can secure confidential data away from people, but if you want our help with doing it, you will need to tell us how you want to define who can see what. Obviously, use SSL as a starter, but within the application, it's a bit more fine-grained - what do you want to show/hide and how do you want to allow/block…
-
It's not "move", it's "display (or not) in different views"
-
It is what it says it is - you've generated a url that is too long for Tomcat to process correctly. You'll need to come up with a shorter JQL query.
-
Go to Admin -> System -> Mail -> Outgoing mail and look for the "prefix" field
-
From memory, you can escape hashes in velocity - use # instead of # So, /## CAUT-IN550332 ##/ would be /## CAUT-IN550332 ##/ in the velocity file. The subject prefix of emails is set in the email settings under the mailserver settings in the admin area.
-
I am sorry, it is not clear what you are asking for here. I can see it is something to do with editing fields, but the sentences do not make any sense. Could you explain it again, in a different way?