youngmon/atlassian-qna huggingface dataset:
When add worklog via REST API(version 2), get 400 if the worklog contains 'adjustEstimate'
Asked by jingga:

When trying to add worklog like below, get 400 as return code. However if I **comments out** the two lines with underscore(++adjustEstimate++ and ++newEstimate++), then will get 201 and the worklog can be added successfully.  
In API user guide <https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-worklogs/#api-rest-api-2-issue-issueidorkey-worklog-post>, those two should be supported.  
auth = self.USER + ':' + self.PASSWORD  
auth = bytes.decode(base64.b64encode(auth.encode('utf-8')))  
headers = {  
'Accept': 'application/json',  
'Content-Type': 'application/json',  
'Authorization': 'Basic {}'.format(auth),  
}  
worklog = json.dumps({  
'timeSpent':'1h',  
**++'adjustEstimate':'new',++**  
**++'newEstimate':'60h',++**  
'comment':'add worklog for trial of auto log jira effort'  
})  
res = requests.request(  
'POST',  
url,  
data = worklog,  
headers=headers  
)


Answers:
author: Prince Nyeche
body: Hey, you can try returning the response to that 400 error to get a better understanding of what the error message says. That will help you to know what's really wrong.

comments: author: jingga
body: What is the "returning the response to that 400 error " ?


author: Prince Nyeche
body: ```
print(res.json())
```


author: Prince Nyeche
body: Do the above in your code on a new line to see what the response is all about.


author: jingga
body: Great thanks [@Prince Nyeche](/t5/user/viewprofilepage/user-id/1928483), below are the error msg, seems the adjustEstimate is not supported

{'errorMessages': \['Unrecognized field "adjustEstimate" (Class com.atlassian.jira.issue.fields.rest.json.beans.WorklogJsonBean), not marked as ignorable\\n at \[Source: org.apache.catalina.connector.CoyoteInputStream@cfc7291; line: 1, column: 41\] (through reference chain: com.atlassian.jira.issue.fields.rest.json.beans.WorklogJsonBean\["adjustEstimate"\])'\]}


author: jingga
body: [@Prince Nyeche](/t5/user/viewprofilepage/user-id/1928483) Do you have more ideas about above error? Seems adjustEstimate is not supported, but this is not aligned with the API user guide for API2 <https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-worklogs/#api-rest-api-2-issue-issueidorkey-worklog-post>,


author: Prince Nyeche
body: You should not use **adjustEstimate** and **newEstimate** as body parameters. They should be used as query parameters instead accordingly to the documentation. Therefore, use it as parameters to your url variable.


author: jingga
body: Great thanks and now according to your suggestions, the interface has been called successfully.


Tags: cloud

rest-api
Enterprise case study
Asked by blake.davies:

Our project management step up leans heavily towards JIRA Software at one extreme and heavily at the other end to Trello.  

We're considering adopting Jira Work Management as our Enterprise PM tool, but are keen to know of / hear from any large organisation that are currently using JWM at scale.  

Can you help connect? We would love to talk through how the adoption is going and understand any insights or learnings.


Answers:
author: John Funk
body: Hi Blake,

All three tools are designed with specific functions in mind. Jira Software for software development teams, Trello for mostly personal functions, and Jira Work Management for Business type teams (non-development).

And all three have their pluses and minuses. So it really depends on the types of things you would be expecting the tool to do. JWM has some really cool features to it, but the boards are very limiting.


Tags: cloud
Does "Issue Collector" exist in Jira Work Management standard cloud solution?
Asked by Anton Faller:

Can customers (people without Jira account) send their request via a form, which then creates a request-related issue/task in our *Jira Work management* board automatically?  
As far as I've understood this kind of form is called *issue collector.*

Background:

I'm testing Jira Work Management in a free demo version, as we think about implementing it in standard license in our custom ski manufactory. When I try to create an "issue collector" for our test-project as admin, I can't find the tab "issue collector" in the settings as described here: <https://support.atlassian.com/jira-cloud-administration/docs/use-the-issue-collector/> .

Thank you for your help in advance!


Answers:
author: John Funk
body: Hi Anton - Welcome to the Atlassian Community!

Take a look at this article.

<https://support.atlassian.com/jira-cloud-administration/docs/allow-anonymous-access-to-projects/>


author: Lukasz Grobelny
body: You can also use Customer Portal for this

Try adding this to your Jira link -\> /secure/admin/ViewGlobalCollectors!default.jspa

comments: author: Anton Faller
body: Thank you, this Customer Portal is a helpful view.

Only, as I was using a free version, I could not implement issue collectors on that page. In standard version this should work though.


Tags: cloud

issue-collector

new-to-jira
Linked issues options Sorting
Asked by Nisath Jabeen Saleem:

By Default when we click on Linked issues the first option we see is "is blocked by" instead I want to see "relates to" since thats the option we widely use

the rest of the options are also used but this is widely used


Answers:
author: Petter Gon?alves
body: Hello [@Nisath Jabeen Saleem](/t5/user/viewprofilepage/user-id/5023769)

Thank you for reaching out.

By default, the issue link type is ordered in alphabetical order by the issue link name, that's why the type "Blocks"/"Is blocked by" is displayed first.

That being said, you can easily change the order of the link types by adding a number before its title - Don't worry about the link name, it will still display as it is today. You can follow the steps below to achieve this:

1. Navigate to your Jira site \> Click at the cog icon at the top-right of the page \> **Issues**
2. under the Section**issue features** , click on **Issue Linking**
3. Click to edit the title of each issue link type you have, adding a number before it as in the screenshot below:  
   ![Screen Shot 2022-09-06 at 6.20.19 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/214593i22352F113FC05F8C/image-dimensions/457x222?v=v2 "Screen Shot 2022-09-06 at 6.20.19 PM.png")

You can check the documentation below for more details about issue linking:

[Configure issue linking](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-linking/)

Let us know if this information helps.


Tags: cloud
how do i create a custom field for address verification?
Asked by maurizio:

how do i create a custom field for address verification?


Answers:
author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

There's not enough context in your question to give you a detailed answer, but what we can tell you is that yes, you can create a custom field and use it for verification. Go to Admin -\> Custom Fields, click "add" and choose a type and what screens it should appear on.

comments: author: maurizio
body: I have to create a field for the verification of the tax code, post code, locality in self-compilation


author: Nic Brough -Adaptavist-
body: Repeating the question is not going to get you a different answer.

Could you explain more about what you're trying to do, and how you are thinking you might hook up Jira to something that can do your verification?


author: Rob Horan
body: [@maurizio](/t5/user/viewprofilepage/user-id/5023332) I think you might need a marketplace app for this. Have you looked at these?

[https://marketplace.atlassian.com/apps/1213678/maps-cloud?hosting=cloud\&tab=overview](https://marketplace.atlassian.com/apps/1213678/maps-cloud?hosting=cloud&tab=overview)

[https://marketplace.atlassian.com/apps/1213257/mapit-for-jira?hosting=datacenter\&tab=overview](https://marketplace.atlassian.com/apps/1213257/mapit-for-jira?hosting=datacenter&tab=overview)


Tags: atl-gruland
priority settings
Asked by Marco Gerhardt:

How can i determine and label the priorities in projects.


Answers:
author: Zoriana Bogutska_Adaptavist_
body: Maybe this discussion can help you <https://community.atlassian.com/t5/Jira-Core-Server-questions/Priority-in-Jira-Work-Management-board/qaq-p/1815218>


author: Sam Nadarajan
body: Hello [@Marco Gerhardt](/t5/user/viewprofilepage/user-id/5023430) - and welcome to the community!

In cloud there's a Priority field you can use. The options here are maintained by your Jira administrator and the options are available for all projects.

As far as determining the priority, that's up to you and your business process. You can certainly use the priority field to determine that. Additionally, you can drag issues up and down - with higher ranked issues reflecting a higher priority for your team.

Hope this helps!

comments: author: Marco Gerhardt
body: Hello Samuel, thank you for your quick help.


author: Lukasz Grobelny
body: Do you want to add priorities to issues?


Tags: cloud
Cron expression for a Scheduled that after 3 days from the date of creation send an email everyday
Asked by Nora Marti:

Hi, Is it possible to make a CRON Expression for a schedule that after 3 days from the creation day an email is sent every day until it change state?

thanks for your help!


Answers:
author: Alex Koxaras _Relational_
body: Hi [@Nora Marti](/t5/user/viewprofilepage/user-id/2818397)

I would create a rule like the following:

![autom rule with cron.png](https://community.atlassian.com/t5/image/serverpage/image-id/214364i939D187B137BB436/image-size/large?v=v2&px=999 "autom rule with cron.png")

* I would schedule the rule to run every day (or workdays) at a specific time
* Then I would narrow down this rule to execute for every issue found within a JQL
* And I would uncheck the "Only include issues that have changed since the last time this rule executed", to make sure that I include all the issues that this query bring.

The JQL I would use would be something like:

```
project = YOU_PROJECT and status = YOUR_STATUS(ES) and created < -3d
```

The created \< -3d will make sure that it will bring you all issue that were created before "3 days ago", meaning that when the rule would run, three days will have already passed.

Of course I would suggest to try the JQL on your instance and make sure that it yield the correct results and adjust it correspondingly.

Let me know if that works for you.


author: John Funk
body: Hi Nora,

I think I would create two rules. The first one would set a value of a custom field when the date hit 3 days from the created date.

Then another that would send be a Scheduled trigger that ran everyday and checked the value of the custom field and the status of the issue.


Tags: cloud
Bulk Clone Professional integration to Jira Portfolio
Asked by Lars Broden:

Good Evening  
My name is Lars Broden and I am the Product Manager for the Bulk Clone 3:rd Party plugins which is on Atlassian Marketplace  

[https://marketplace.atlassian.com/apps/1213028/bulk-clone-professional-for-jira?hosting=datacenter\&tab=overview](https://marketplace.atlassian.com/apps/1213028/bulk-clone-professional-for-jira?hosting=datacenter&tab=overview)  
[https://marketplace.atlassian.com/apps/1210727/bulk-clone-basic-for-jira?hosting=datacenter\&tab=overview](https://marketplace.atlassian.com/apps/1210727/bulk-clone-basic-for-jira?hosting=datacenter&tab=overview)  

We have some customers of our plugin Bulk Clone Professional that is also using Jira Portfolio and would like to BulkClone "Child Issues" and as a result would like to have the "Parent Link" field migrated to the cloned parent issue in case they want to clone a parent issue and it's child issues.  
In order to accomplish this we need to be able to edit the "Parent Link" custom field value from Java, from our research so far it seems that the value for the field is a custom Portfolio object (not an IssueImpl object)?, and we cannot update the value of the field as a consequence of this.  
Is there a way we could do this from Java?, The "Epic Link" field for example stores an IssueImpl object as it's value and that type is available in the API and we can edit values for it. Could you guide us in the right direction?   

The way we try to set the value is via "field.updateValue(obj1, obj2,...)"  

Would appreciate a quick feedback on this as we have clients awaiting an imminent release supporting this and we are currently stuck/blocked to proceed  

Best Regards  
Lars Broden  
LB Consulting Group AB  
Moible: +46 (0) 709 56 58 43


Answers:
author: Thomas
body: Hi [@Lars Broden](/t5/user/viewprofilepage/user-id/640995) ,

Portfolio Parent Link information is stored in the issue properties (see entity_property table) that is accessible via the Jira REST and Java API (e.g. <https://developer.atlassian.com/server/jira/platform/entity-properties/>)

The issue property is essentially a JSON blob that may contain multiple values (this is the case for Portfolio) so be sure not interfere with those, depending on how you interact with those values.

Also, those fields require to be in the Jira Lucene index so depending on how the issue gets modified, be sure it gets re-indexed!

Cheers,

Thomas

comments: author: Lars Broden
body: Thanks, Thomas, we will try this and see if it will work


Tags: advanced-roadmaps

atl-dev
Once you commit changes made in Portfolio into JIRA , how do you use Portfolio to re-simulate
Asked by Gil Groman:

Once you commit the changes made in Portfolio Plan into JIRA, each story is assigned a sprint.   
To my understanding this prevents Portfolio from moving these stories in its next plan simulation (sandbox). so we are left with a fixed plan that only way to re-plan it is by moving back all stories from Sprints to Backlog.

How should you use Portfolio to re-simulate after the first Plan commit?  

Note: we are working with the non-improved interface.


Answers:
author: Earl McCutcheon
body: Hi Gil,

A commit finalizes that the values and sets them on the issue. Once you commit a value to the sprint field the sprint is set and as you noted needs to be cleared to make changes to the plan as the [scheduling algorithm](https://confluence.atlassian.com/jiraportfoliocloud/scheduling-behavior-828785428.html) is using the sprint field as one of the weighted items to calculate the issues position in the scope. So once the sprint is set it anchors the issue to that committed sprint location.

If there is not an active or future sprint avaliable to add an issue too, Portfolio will populate a logical placeholder sprint that will not anchor the issue to that committed sprints location and use the alternate scheduling factors in the schedule.

So if you are looking to have more leniency in the sprint commitment you can set up your sprint planning more ad-hoc by only having the current sprint created then only create future sprints where the resources commitment can be confirmed, so that portfolio will place issues into the logical place holder sprints when running the calculations based on the other scheduling factors vs using the committed values of the sprint for the scheduling factors.

Regards,  
Earl

comments: author: Gil Groman
body: Thank you Earl,

This is what was our understanding as well (and work like that with some groups)

It does raise couple of more questions on they way we could work and get specific reports, so I will open these in a different thread.  

Thank you again,

Gil


Tags: advanced-roadmaps
Portfolio Improved Interface will not use points from stories to estimate sprints, only epic level?
Asked by Matt Marcus:

Using the improved interface of Portfolio and trying to map out future sprints based on points from stories. These do not appear to count against the velocity at all, however if I only add the points on the parent epic the points will be evenly split across sprints.

Why won't the individual stories' points be counted toward the projected sprint?


Answers:
author: Dave
body: Hi [@Matt Marcus](/t5/user/viewprofilepage/user-id/680643) ,

Can you confirm which version of Portfolio that you're using please?

Judging from your description it looks like you're not actually assigning the issue to a sprint. When you group by team and choose to view capacity on the timeline you will see the sprints (if there is a board associated with the team)... it looks like you've reached this point already!

When you assign story levels to sprints (rather than just setting target start and end dates for the sprint) then you will see the capacity changing.

However, when you set the dates for an epic we will actually distribute the story points over the span of sprints that it covers (as you've also discovered).

Although we made a conscious decision to not distribute the points from story level issues based on target dates, we're actually looking at making some changes to this behaviour to improve the way that capacity is reported. Can I ask that you e-mail us at portfoliofeedback@atlassian.com so that we can discuss this in more detail with you as we're keen to get some feedback on the current behaviour and our proposed changes.

Many thanks,

Dave


Tags: advanced-roadmaps
Versioning & releases
Asked by Another agile delivery person:

Hi,

New to the community \& fairly new to Jira, so be gentle! Could someone let me know what the best practises are around versioning of the Jira artefacts please.

My intention is to use Jira portfolio in order to provide visibility of the various teams work we have ongoing. For this, I understand that I have to use the FixVersion field.

What is the best practise here? We have a fairly standard portfolio heirarchy of Themes, initiative, Epics, stories, subtasks etc.

Should say Themes have FixVersions, and should these be all the Fixversion of the various Epics, Epics just contain one FixVersion and all its children stories have the same FixVersion of the Epic?

Sorry, bit of a ramble, but wondering if there is a best practise here, or perhaps there are some guidelines somewhere?


Answers:
author: Ashkan Malekly
body: Hello [@Another agile delivery person](/t5/user/viewprofilepage/user-id/3556530)

At first wellcom to community and wellcom to Jira. you have very good idea nad this way is best and what you say about portfolio exactly correct.

comments: author: Another agile delivery person
body: Ok, but still not sure here

We have a number of Epics that each refer to subcomponents of the overall product release.

I have versioned all the Epics with the same version number let just say is called product_release_1.0

The stories under each of the Epic are versioned by their sub component name, so lets say we have three epics each have three stories under them

Epic1 -\> versioned (product_release_1.0)

Story1 - \> versioned (sub_component_1

Story2- \> versioned (sub_component_1

Story3- \> versioned (sub_component_1

Epic2 -\> versioned (product_release_1.0)

Story1- \> versioned (sub_component_2

Story2- \> versioned (sub_component_2

Story3- \> versioned (sub_component_2

Epic3 - \> versioned (product_release_1.0)

Story1- \> versioned (sub_component_3

Story2- \> versioned (sub_component_3

Story3- \> versioned (sub_component_3

I then use portfolio in order to track the progress on the subcomponent development and the overall product release.

Does this sound like a sensible approach, you could of course say look at portfolio and see if it looks sensible, unfortunately the way the team have been working i.e. unpointed story points, stories being bumped over many iterations, lack of dependencies, no version labels, have all made portfolio look a bit of a mess.


Tags: advanced-roadmaps

cloud
Is there a way to map children to any higher parent?
Asked by Taleena Herkenhoff:

I have added two hierarchy levels above Epic - Objective and Initiative.

I would still like the ability to set either Objective or Initiative as the parent for a given epic. However, currently it looks like the parent MUST be the hierarchy level directly above - it can't skip a level.

I found a thread explaining this is not currently possible:

<https://community.atlassian.com/t5/Jira-questions/Will-adding-a-level-in-the-Jira-Portfolio-hierarchy-break/qaq-p/1039628>

And that this is the fix, but for some reason I cannot vote for it:

<https://jira.atlassian.com/browse/JPOSERVER-2350%C2%A0?_ga=2.9756278.2110597617.1569876482-1210054755.1546533562>


Answers:
author: Ste Wright
body: Hi [@Taleena Herkenhoff](/t5/user/viewprofilepage/user-id/3495095)

I've checked the suggestion and I can vote for it - are you sure you're logged in for the suggestions lists?

The previous answer is still the same at this stage - grandfather links are not possible using the standard hierarchy.

You'd need to consider a sibling link to show a relationship between Epic and the grandfather. Although this doesn't show up in Portfolio - it's just a method to show a relationship which isn't limited by the hierarchy.

Ste


Tags: advanced-roadmaps
How can I view cross-projects releases on a timeline?
Asked by nph:

Hi everyone,

How can I view clearly cross-projects releases -defined in Portfolio- on a timeline?

Thanks

Nghia


Answers:
author: Earl McCutcheon
body: Hello Nghia,

Thanks for reaching out to the community and welcome.

To get a better view on the issues in a particular release you can use the Plan's filter options to show only issues in the cross project release. When setting the filter the cross project releases will be categorized under a header for easy identification, followed by the project specific releases like this:

![Screen Shot 2019-10-07 at 2.05.00 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/68659i89200F9C99044BC6/image-dimensions/163x198?v=v2 "Screen Shot 2019-10-07 at 2.05.00 PM.png")

Regards,  
Earl

comments: author: nph
body: Thanks Earl. Unfortunately this is not exactely what I'm asking for.

I would like to specifically view the cross-project releases (name and date) on the TIMELINE. Is it possible?

Currently the best I can have is a vertical line on the timeline for each cross-project releases but with no name on each vertical. So it's hard to know which is which.


author: Earl McCutcheon
body: Hello Nghia,

Ok, Got ya and thanks for the clarification, and this can partially be done, just not as a single entity.

First the release dates are not able to be shown on the timeline directly in a location like a field per issue due to the dynamic options avaliable for releases which would clutter up the timeline with excess details. So to get the better view of the Release details from the Roadmap tab looking at the Verticals you mentioned, if you click the dot at the top of the timeline, when selected it displays details on which release is scheduled for that date, so you do not have to switch back to the release tab for the additional details, EXE in the following screenshots of the overview and drilling down into the overview details, noting Cross project releases are taged with a grey box next to the name to call them out as a cross project release and make identification eaiser:

![Screen Shot 2019-10-15 at 4.56.26 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/69510i090E294C853B022D/image-dimensions/126x87?v=v2 "Screen Shot 2019-10-15 at 4.56.26 PM.png") AND ![Screen Shot 2019-10-15 at 4.57.42 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/69511i51FCF36A627DCF02/image-dimensions/95x77?v=v2 "Screen Shot 2019-10-15 at 4.57.42 PM.png")

For the name portion this can be isolated for easier identification using the "View Settings" options and setting the "Group By" filter to "Release", under this view the issues are collected and nested under each release and again there is a Grey Box next to the release and they will then show the groupings and cross project releases like this:

![Screen Shot 2019-10-11 at 1.42.41 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/69507i104E2557F0AB3AA8/image-dimensions/110x93?v=v2 "Screen Shot 2019-10-11 at 1.42.41 PM.png")

Regards,  
Earl


Tags: advanced-roadmaps