Comments
-
That setting will enable html markup, but not scripting. As far as I can tell, the only javascript you can inject now has to go into the announcement banner. Or, you can use add-ons to get it in there.
-
Yes - Atlassian are removing the ability to execute arbitrary code such as javascript in descriptions, as they're a security (and sometimes, stability) risk. It's not configurable.
-
Ah, fantastic you've found it! I'm glad my ramblings lead you to go back over the config. I must admit, getting the right scheme applied is something I get wrong all the time too. I've got used to checking and re-checking lots of times.
-
No, it's the board columns that we're interested in. The columns that appear in the working view / active sprint display. Go to board configuration and look at the column setting - each column should contain one or more status, we'd like to see which status are in the far-right column.
-
Great, can we have a look at the second sheet, and also, can you tell us what status are in the far-right hand column on your board? (There may be more than one)
-
I'm afraid there's no way of rearranging the fields at this time. Not without hacking your own code into it.
-
Weird one! But there's https://support.atlassian.com/contact/ - raising a support request will get it turned into a bug if appropriate.
-
It should be. I'm not a proper coder either, but I think you'll want something that can get the list of users in a group, and check if the issue.reporter is in the list. I would say check for groups in issue.reporter.getGroups(), but there is easy getGroups() function and no way to directly read a user and say "what groups…
-
You'll need some code to do that as I read it. You can do "current user is the reporter and the current user is in group X" off-the-shelf. But I think you're asking for "Check that the reporter of the issue, Chuck, is in group X, when Dave is trying to perform the transition", which is not an option you have. I'd use the…
-
Code. You'll need to find or write an add-on that can add attributes to versions.
-
No, you're just failing to answer the question, the same way the thread starter did. 80% of WHAT? Money? Time? Bricks? Cake? Let me put it this way: You say "80% complete". Do you mean you've spent 80% of the money? When will it be done? Is 80% of my house physically built? What?
-
That's a circular answer that does not answer the question. 80% progress means I've done 80% of it. What does 80% done mean? What is it measuring? I've already explained that "progress" is meaningless because you aren't measuring anything. What is the 80% actually OF? A percentage without knowing what it is a proportion of…
-
Best installation option is Admin -> Manage applications
-
JIRA Software provides functionality for Sprints (i.e. boards, backlogs, and sprint reporting), as well as Kanban. You can add it to your Cloud system, as a trial via admin -> manage applications
-
We can't really answer that, as it depends on your systems and usage. But If you want to have any form of crossover between the two, then adding JSD to a Software installation is by far the better option. Your JSD Agents will be able to ask developers for help, including them in support issues, and have quick-create-issue…
-
Ach, Thomas beat me again ;-) When you raise the request, I would give them the date and time you last had a failed document import - that narrows down where they need to look in the logs.
-
Ok, let me put it another way. It is useless because it tells us nothing. "Progress" is a "suitcase word". It has a generally understandable concept (suitcase = a box full of things I carry), but tells you nothing about the actual meaning. "This is 80% complete". As a user, looking at an issue with that on it, what does it…
-
Ok, the best way to get to it from here is probably: 1. Make a note of the sprint you are questioning (Looks like Sprint 27 to me, but I'm not sure if it was just demo data for a screenshot) 2. Go to Board -> Configure and look at the first page of options called "General", where there is a board filter defined. Beneath…
-
I think you're missing the point. I'm not complicating anything, I'm simply pointing out that there is no definition of "progress" here, so we can't answer the question. What are you measuring? Time spent vs estimate? Story points? How many lego bricks you've added to the model?Without knowing what you are measuring,…
-
That doesn't sound quite right, although I'd be interested in the board config too - what status is in the far right-hand column on the board, and which issues are in it? Is it possible to give us the filter I asked for? (It's not going to leak your data to use - the fields I've asked for are pretty abstract)
-
This is a very poor design, or at least data and process mapping into JIRA. Your workflows should match your process. You don't have two processes here, you have one, so you should really have one workflow to match it. Also, generally, issue types are not something that should change as part of the process. Bugs don't…
-
Yes. It's one of the things you have to educate your users about if you do decide to use issue security.
-
So what are the last lines in the logs? If they really do just end with nothing, then it's the operating system killing the Tomcat container in the hardest way it can, not even a clean shutdown. That suggests poorly configured memory settings or a process that is killing off others.
-
There's three problems here. 1. It sounds like your post-function is associated with the create on all issues, so the code is executing many times 2. Deleting issues in JIRA is generally a bad idea, as it completely destroys them 3. Deleting an issue within a post-function is potentially suicidal in terms of data integrity…
-
If a user cannot see an issue, then they get no information about it. They can work out that it is or was there, as they will see a "hole" in the issue numbers, but nothing else. They won't know if the 5 issues are secured or deleted, and the system will behave as though they've been deleted for that user. So, it is…
-
Theres a couple of conceptual problems with this First, in the real world, an issue type is usually not something you would generally change. To change it regularly implies you're using it to represent the wrong thing. When it's a bug, it's always a bug, it's not going to morph into a story or an epic, unless it was raised…
-
Use JIRA. Can't tell you a lot more than that, the technology behind that site is JIRA.
-
I can't help but agree with Rachel here. "Move" has three basic use-cases: * A mistake where someone put it in the wrong project * The issue type needs to change * Merging projects If you are trying to use "move" as part of a standard process, then my instincts are screaming "broken process"
-
No, sorry, I was not clear there. I'm saying what you are seeing is incorrect behaviour if everything is configured correctly. The red indicator shows that the field is set to mandatory by the field configuration, so we can forget my thought that it's "a flow thing" I think we need to see your field configuration scheme…
-
That's wrong. It's certainly not what it should be doing. Makes me suspect that your field config scheme is not mapping them correctly. Or it's a flow thing - when you create a task, does the screen show the red * for mandatory?