Comments
-
Edit the workflow and add a transition back to "in progress", then use it. There is no "undo", but the workflow is very flexible.
-
Yes you can rename fields. I'm not sure what the second comment means. Service Desk replies to the person who emailed it.
-
You can't do it with "edit" natively. You could put a workflow validator on the transitions where it is important to make it mandatory before things can move through the workflow. Or install something like ScriptRunner which has a Behaviours module tht can make a field mandatory on screen.
-
There is no "script" for this. Please re-read the first part of my answer.
-
You can swap it - see https://confluence.atlassian.com/jirakb/disable-relative-dates-in-jira-applications-414187622.html
-
The ~ text searches are "fuzzy" - it's finding something it thinks is similar enough to [name] that you might want to see it. The problem with fuzzy text searches is that they do have a nasty habit of throwing up the odd googly ball. While you'd sort of expect a fuzzy search given "crat" to return thinks like "cat, chat,…
-
You have no access to the system level stuff on Cloud. I believe Atlassian support will change it for you though, if you raise a request at https://support.atlassian.com
-
Log in as an admin, click the admin cog at the top right, select system. If you don't have "system" on the list, then you don't have the admin rights you need.
-
You can get a new licence for a different number of users in your my.atlassian account. To change the base url, first make the new url available on your network, and then change JIRA's configuration in "general settings" to match the new url
-
No, you're in the right place. I think we've covered your recent comments already.
-
Ok, Another sanity check which I think you've probably already performed - they're definitely in the status "done"? Would it be possible to re-index the issues and see if that fixes it ? You can re-index the whole project they are in, or just update one of them with something minor, like adding a . to a text field.
-
Do the issues with status done that are appearing actually have a resolution date set? The status is not techinically anything to do with the resolution.
-
Towards the end of your error message, there's a line that says your field is failing. You are giving it a date, but the field appears to be trying to convert that to a text format. Or possibly the other way around, but either way, the code in your field does not know how to handle the incoming data.
-
They're deleted. Gone. You'd need to do an undelete at the operating system level to recover the physical file.
-
Just put the "story points" field on the create and edit screens. (Assuming you're using that field for it)
-
A request is a Service Desk front end for the customers, which simplifies the presentation of an issue to them. The status on a request is related to, but not the same thing as the status on the issue behind the request. It looks to me that your email is being generated for an issue that does not have a request in front of…
-
I suspect your database is damaged. It might be possible to rescue it, but it's usually a lot of work, adn you should simply go back to the last backup you took, or get a fresh copy of production (as this system is a dev/test one, not live)
-
All I can go on is my experience of finding tens of thousands of stories with nothing by the default text in them. In some places, it might be fine. In the places I've seen, it fails.
-
Javascript is not my strength, I'm afraid I have none that might help.
-
This is not even a question. But, have you tried reading the documentation for the add-on?
-
Ok, it sounds like your code is trying to use a request status for issues that don't have one because they're not service desk issues, or the status of the issue is not mapped to a request status.
-
It's not asking you to have an order by clause, it's just saying "if you have one, you need to remove it first". You don't seem to have one, so you don't need to remove anything. The second part of the fix is to add the correct sort order. Assuming your filter is "project in (PRW, AGS, KVB)", you need "project in (PRW,…
-
I think you need to look at where the code came from and what you're trying to do with it. Do you know that $request.status is a supported variable?
-
You should go back to a template that was working before the changes to begin with.
-
From the word "project", I'd take a guess you mean JIRA. Please could you confirm that? If so, then the answer is generally that you don't - you modify the existing ones, to take account of your business logic. Emails are sent by event, not project.
-
Does the issue key come out alright? Did the ${request.status} come out before you made your changes?
-
You do need add-ons to do this, there is nothing built into JIRA that creates sub-tasks. There are plenty of options in the marketplace. Bob Swift's issue creator, JMWE, Automation and Scriptrunner are quite powerful, sort of allowing you to code directly in the core of JIRA. Others are a bit more "fixed", where they'd let…
-
You could write your own email handler to do your more involved business rules.
-
There's a post-function for "set field" which will enable you to set a specific user as the reporter on issue creation.
-
I'd use the Script Runner add-on, but there are others in the marketplace that might be able to do it. Try typing "workflow" or "condition" into the search.