nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

It will be possible create an issue with Resolution different from Unresolved

fabio marcelo

Hi All,

Please , It will be possible create a new issue with the resolution equal "Initial" ?

Everytime that i create a new issue the resolution is set to Unresolved.

Please could you help me ?

Thanks in Advance

Fabio

Accepted answers

All comments

Matheus Fernandes

This can be achieved by setting up a Update Field post-function in the Create Issue transition of your workflow and setting it to update the Resolution field. Basically, you'll need to:

Go to Administration » Workflows

Click the link for the workflow in 'Steps' column

Click 'Open' link in the Step Name column

Click 'Create Issue' link in the Workflow browser (the inbound transition that arrives into the Open step)

Add a post-function, 'Update Issue Field', and set the Resolution field to desired value (if necessary, create a draft so the workflow is editable)

fabio marcelo

Hi Matheus,

Thanks for your help.

I tried it with the value "Not Started" but the issue continue being created with Resolution = Unresolved

Follow my workflow:

Create Issue --> Draft --> Open --> In Progress --> Closed

In the first status Draft the issue is with Resolution = Unresolved

Is there any way to set this field Resolution to "Not Started" when i create the issue ?

Thanks in Advance

Fabio

Nic Brough -Adaptavist-

Does the user creating the issue have the "resolve issue" permission?

Joe Pitt

Not a good idea. The 'Assigned to Me' built in filter, along with many others, rely on the resolution field being empty, which is the condition for UNRESOLVED. If you populate it with ANYTHING the filters will not show any issues. Not Started sounds more like a status in a workflow than a resolution to an issue. You can change the workflow to show Not Started instead of Open.

fabio marcelo

Hi Nic,

Yes, the user have the "resolve issue" permission.

The problem to set the resolution only happens in the creation from issue.

When i changed the issue to "Open" the post function change my Resoluon to "Initial

Please o you have any other idea?

Thanks in Advance

Fabio

Nic Brough -Adaptavist-

Yup,

I was assuming Fabio had understood that any issues created with this would be automatically considered as "closed" by most of Jira. I shouldn't assume that people know this stuff...

fabio marcelo

Hi all,

Let me explain better my problem.

We are using the plugin commit acceptance to block commits in SVN.

The commmit only is accepted when the Resolution from issue is "Unresolved".

The resolution only can be Unresolved when the status was "In Progress", so the commmits only will be permitted in the status "In progress".

But when i created the issue, his status is Draft and the resolution is Unresolved, so in this case commits will be accepted, but i would like to change this resolution on creation from issue for that this resolution was different from Unresolved with the objective from block commmits.

Thanks in Advance

Best Regards

Fabio

Renjith Pillai

Fabio,

Rather than changing the default JIRA behaviour by setting the resolution initially, you can probaly achieve this by a simple change in the SVN hook script that you are using. I have not tested it, I just read the code (I am assuming perl script):

Locate the line "my $result = $s->call("commitacc.acceptCommit", $jiraLogin, $jiraPassword, $committer, $projectKey, $commitMessage)->result();" in the perl script
Add the below code (after that line):

$comment =~ m/($projectKey-\d+)/;
my $issue = $s-&gt;call("jira1.getIssue", $jiraLogin, $jiraPassword, $1)-&gt;result();

Add this line after "($acceptance, $comment) = split('\|', $result);"

if($issue.status() == "Draft")
{
 $acceptance = 'false';
 $comment = "Commits not accepted when the issue is in Draft state";
}

fabio marcelo

Hi Renjith,

Thanks for your help.

I tried to do this but show me the error :

Please could you help us ?

To open Jira here it s necessary 2 authentication.

First in the portal and other in the JIra tool , the problem could be it ?

Thanks in Advance

Best Regards

Fabio

fabio marcelo

Hi Nic and Renjith,

Please dou know the reason from the error that i mentioned above ?

Thanks in Advance

Fabio

Nic Brough -Adaptavist-

You've got two - the second one MIGHT be caused by the first (I don't know perl well enough to tell you if that's the case). The first error is in the regular expression you're using. The second a connection error. Pretty much what the error messages are telling you - your code is wrong, and the connection possibly broken.

Norman Abramovitz

Could this just be a simple language translation issue? My resolution database table does not contain a row for the unresolved resolution type, so I was guessing the unresolved resolution must be defined somewhere else.

I found this reference in one of the issue field resolution vm files:

$i18n.getText('common.resolution.unresolved')

I found these references in the english uk language pack file:

# resolution
common.resolution.UNRESOLVED = UNRESOLVED
common.resolution.unresolved = Unresolved

So, maybe just updating your language packs, you can get a different word to display for unresolved.

fabio marcelo

Hi Norman,

Thanks for your help.

Sorry, how can i update my language packs ?

Thanks in Advance

Fabio

fabio marcelo

Nic,

Please did you find any error in the script above ?

Thanks in Advance

Fabio

fabio marcelo

Hi Nic, Norman and Renjith,

Finally i got create a issue with resolution different from Unresolved.

It s missing

the store the update issue value after of create the issue

Follow my Post Function:

Add a new post function to the unconditional result of the transition.

Creates the issue originally.

— THEN

Assign the issue to the reporter.
Move Up | Move Down | Delete

— THEN

The Approved of the issue will be set to No.
Edit | Move Up | Move Down | Delete

— THEN

The Resolution of the issue will be set to 13.
Edit | Move Up | Move Down | Delete

— THEN

Stores updates to an issue (no change history is created).

— THEN

Re-index an issue to keep indexes in sync with the database.

— THEN

Fire a Issue Created event that can be processed by the listeners.
Edit

Norman Abramovitz

Follow the answer here to update your language packs.

https://answers.atlassian.com/questions/66852/language-files-appear-not-to-be-present-in-jira_root-atlassian-jira-web-inf-lib

Here is

0) Locate your JiraWebActionSupport.properties file if and only if you are using the default english language. Otherwise follow the directions to find your language pack as noted in the url above.

2) Edit the file JiraWebActionSupport.properties or your language pack properties file after it is unpacked in a text editor

3) Search for the word resolution and you should find these lines

# resolution
common.resolution.UNRESOLVED = UNRESOLVED
common.resolution.unresolved = Unresolved

4) change the values after the equal signs

common.resolution.UNRESOLVED = INITIAL
common.resolution.unresolved = Initial

5) Save your changes and repackage your language package if and only if you are updating a language pack

6) restart Jira

Any new issue without an resolution value should be showing one of your new values.

Matheus Fernandes

Also, what is the ordering of the post-functions?

You have to set it right after the "Create Issue" post-function, if I'm not mistaken.

Norman Abramovitz

You might need to disable your post functions or display an older issue where the post function was not applied and is showing unresolved.