Differences

This shows you the differences between two versions of the page.

--- iqxweb:changelog:v1.3.0 [2019/02/28 14:53] – Gareth Johnstone
+++ iqxweb:changelog:v1.3.0 [2021/11/18 15:58] (current) – Gareth Johnstone
@@ Line 1: / Line 1: @@
+WIP
 ====== [DRAFT] IQXWeb v1.3.0 Release Notes ======
 ===== [IW-622] Client Portal - Current Reqs, visibility of Perm Reqs. =====
-=== JIRA Description ===
-Seems to show forever - there is no finish date for perms, expiry is wrong, not sure yet what it should be
-Show if its not in the final state
-The requirements can be limited via the procedure?
-see comment made by A Developer below
-Procedure is: NetClientRequirementList \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 20: / Line 10: @@
 ===== [IW-623] Client Portal, Reqs - Previous - Cand details - does not show if on Short List and what state =====
-=== JIRA Description ===
-You can select and it updates IQX but does not show on Details what current state is.
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18444/image-2018-08-15-18-00-28-414.png}}
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18443/image-2018-08-15-18-00-58-945.png}} \\ \\
 === JIRA Release Notes ===
 Fixed bug where, when updating a candidates status in current requirements it would not show. \\ \\
@@ Line 34: / Line 18: @@
 ===== [IW-745] Print button on registration WEBFETCHTERMS =====
-=== JIRA Description ===
-After the department select you will see the terms and conditions for that department, add a print button to it. \\ \\
 === JIRA Release Notes ===
 Print button added to department terms and conditions pages in the registration wizard. \\ \\
@@ Line 47: / Line 28: @@
 ===== [IW-784] Requirements can only be added by the vacancy contact - undesired behaviour =====
-=== JIRA Description ===
-Suppose the client Nikola Pearson attempts to add a requirement for a vacancy she is not the vacancy contact for.
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18709/image-2019-01-07-17-30-44-879.png}}
-in this case Jo Turner who works at the same company is the vacancy contact. When Nikola attempts to add a requirement, an Error [object Object] appears:
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18708/image-2019-01-07-17-32-58-345.png}}
-Now, when the Vacancy contact is changed to Nikola Pearson:
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18707/image-2019-01-07-17-33-42-731.png}}
-Now Nikola can successfully add the requirement:
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18706/image-2019-01-07-17-34-15-597.png}}
-Can this be changed so that other nikola could add the requirement even though it is owned by Jo? \\ \\
 === JIRA Release Notes ===
 Fixed issue where if a client was not the contact for a vacancy, they could not add shifts to it \\ \\
@@ Line 71: / Line 36: @@
 ===== [IW-786] Bank Details  procedure to also update Payment Method to BACS if details added =====
-=== JIRA Description ===
-As a user, if a cand joins without bank details they are paid as cheque.
-If a Cand updates bank details on web the payment method remains cheque, which is a problem.
-Suggest procedure as well as updating bank details also updates the pay method AND the view changes title to say 'In order to be paid by BACS please add bank details'
-There is the question is should bank details be blanked online should pay method be changed. Will ask BR for opinion.
-updated view with info message. \\ \\
 === JIRA Release Notes ===
 When a candidate adds/updates their bank details they pay method will be set to BACS \\ \\
@@ Line 91: / Line 46: @@
 ===== [IW-787] Save and Continue when adding current requirements =====
-=== JIRA Description ===
-When adding shifts, have a save and continue button \- so when its saved it clears the form (minus the selected shift).
-When the save button is clicked and the shifts have been saved, add the saved shifts to a list so the client can see what has been added. \\ \\
 === JIRA Release Notes ===
 Save and Continue button added to add shifts page in current requirements. \\ \\
@@ Line 103: / Line 54: @@
 ===== [IW-788] Client - Current Requirements - Shifts ability to book previous temp =====
-=== JIRA Description ===
-When clicking on a shift, show previous temps and allow client to book them for that shift<del> if in suitable state and not withhold and are available and compliance </del> use existing IQX Functions \\ \\
 === JIRA Release Notes ===
 A client with the right 'FILLJOBS' enabled will be allowed to book a previous candidate straight into a shift. (The candidate still has to accept this via their diary) \\ \\
@@ Line 115: / Line 63: @@
-===== [IW-789] ASA - shift information not appearing? =====
+===== [IW-789] shift information not appearing? =====
-=== JIRA Description ===
-The assignment details view appears blank. I think this is a custom form for them?
-Custom procedure has been overwritten with our standard one - theyre custom one needs added back on \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 127: / Line 70: @@
 No information from GitHub
-===== [IW-789] ASA - shift information not appearing? =====
+===== [IW-789] shift information not appearing? =====
-=== JIRA Description ===
-The assignment details view appears blank. I think this is a custom form for them?
-Custom procedure has been overwritten with our standard one - theyre custom one needs added back on \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 139: / Line 77: @@
 No information from GitHub
-===== [IW-790] ASA - client report "details for booked shifts" not appearing to work =====
+===== [IW-790] client report "details for booked shifts" not appearing to work =====
-=== JIRA Description ===
-When running this report, the output appears to be a bunch of SQL errors. \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 150: / Line 85: @@
 ===== [IW-791] Avatar/gravatar - Can this be styled to fill the space if switched off? =====
-=== JIRA Description ===
-Currently when switched off it looks like this:
-{{https://iqx-limited.atlassian.net/secure/thumbnail/18723/image-20190110-111808.png}}
-Can this be tidied? Maybe center aligned or box stretched, whatever is a good solution visually.
-I imagine this would need to shrink back to its original size if the gravatar was switched on. \\ \\
 === JIRA Release Notes ===
 Settings all moved to a settings page.  Logout menu restyled.  Send bug report and help buttons added.  Send feedback button also added to all portals except candidate. \\ \\
@@ Line 168: / Line 92: @@
 Created new settings page and re-arranged log out menu and made it look a bit nicer - check jira for screen shots.
-===== [IW-792] ASA - Help page error =====
+===== [IW-792] Help page error =====
-=== JIRA Description ===
-When attempting to access the help page \- see screenshot
-{{https://iqx-limited.atlassian.net/secure/thumbnail/18724/image-20190110-112022.png}} \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 184: / Line 101: @@
 ===== [IW-793] Client portal - charge rate shows as "pay rate" =====
-=== JIRA Description ===
-In the client portal, the charge rate has the heading of “pay rate”.
-Timesheets \\ \\
 === JIRA Release Notes ===
 No changes. \\ \\
@@ Line 196: / Line 108: @@
 ===== [IW-794] Procedure for [IW-788] =====
-=== JIRA Description ===
-Procedure for {{https://iqx-limited.atlassian.net/browse/IW-788}} \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 206: / Line 115: @@
 ===== [IW-795] Procedure for IW-786 =====
-=== JIRA Description ===
-Procedure for {{https://iqx-limited.atlassian.net/browse/IW-786}} \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 216: / Line 122: @@
 ===== [IW-796] Error when clicking currentrequirements/line/previous/candidate name =====
-=== JIRA Description ===
-NetClientRequirementShortList returned a result set with a different schema than expected | currentUser: A Stephens, A & M Stephens | {"options":{"fetchAPI":"callresult/NetClientRequirementShortList?pRowID=XX13NNVS060120140000&IsShift=0","fetchTarget":"ShortListed","multiRow":true}} \\ \\
 === JIRA Release Notes ===
 Fixed issue with db procedure \\ \\
@@ Line 227: / Line 130: @@
 ===== [IW-798] Date format on completed timesheets heading "Completed by" appears in YYYY-MM-DD =====
-=== JIRA Description ===
-{{https://iqx-limited.atlassian.net/secure/thumbnail/18727/image-2019-01-11-17-05-10-290.png}} \\ \\
 === JIRA Release Notes ===
 Fixed issue with date being in the wrong format on completed timesheets. \\ \\
@@ Line 240: / Line 140: @@
 ===== [IW-799] previous temps - sort by using most recent timesheet date instead of Keyname? =====
-=== JIRA Description ===
-No Description from JIRA \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 250: / Line 147: @@
 ===== [IW-799] previous temps - sort by using most recent timesheet date instead of Keyname? =====
-=== JIRA Description ===
-No Description from JIRA \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 260: / Line 154: @@
 ===== [IW-801] Error message after page 2 of registration wizard submitted =====
-=== JIRA Description ===
-{{https://iqx-limited.atlassian.net/secure/thumbnail/18733/image-2019-01-17-12-27-01-636.png}}
-Error appeared after page 2 of registration wizard was complete. \\ \\
 === JIRA Release Notes ===
 Fixed issue with registration division selection \\ \\
@@ Line 272: / Line 161: @@
 ===== [IW-802] Update copyright notice date =====
-=== JIRA Description ===
-No Description from JIRA \\ \\
 === JIRA Release Notes ===
 Updated copyright notice year \\ \\
@@ Line 283: / Line 169: @@
 ===== [IW-803] version bump =====
-=== JIRA Description ===
-No Description from JIRA \\ \\
 === JIRA Release Notes ===
 REMOVE FROM RELEASE NOTES \\ \\
@@ Line 294: / Line 177: @@
 ===== [IW-805] Ability to see Web Version number on front end of portal =====
-=== JIRA Description ===
-A common issue is not knowing and not being able to easily find out what version of Web a particular client has.
-It would be useful to have a mention of the version perhaps on the bottom left/bottom right of footer, e.g. "Version 1.2" - that way we can more easily troubleshoot client issues. \\ \\
 === JIRA Release Notes ===
 Added version number to the portal \\ \\
@@ Line 310: / Line 188: @@
 ===== [IW-808] Password reset for mobile site - to include Login ID (Consultant) =====
-=== JIRA Description ===
-Change the NetForgottenPassword procedure to look up the user based on EmailAddress rather than loginid
-This will allow consultants to change their password via the online form rather than having to rely on using IQX (useful if they are out and about)
-The procedure will also need an order by on the set PersID (line 6) to stop the procedure from producing an error on newer version of SQLAnywhere
----------------
-Original Ticket
----------------
-Freshdesk Ticket #12419
- [cid:image001.png@01D4B943.BCCD3720]
-Kind regards
-Lisa Dowling
-Training Coordinator
-BCL Legal
-t. 0161 8197475 f. 0845 241 0931
-rd Floor, Lancaster Buildings, 77 Deansgate, Manchester, M3 2BW
-Offices in Manchester Leeds Birmingham London Liverpool and Bristol
-[cid:image001.jpg@01CF21AC.130A08F0]  Follow us on Twitter<http://twitter.com/#%21/BCLLegal>  [cid:image002.jpg@01CF21AC.130A08F0]  Connect with us on Linkedin<http://www.linkedin.com/company/398168>
-www.bcllegal.com<http://www.bcllegal.com/>
-For details of our most recent salary survey click on
-http://www.bcllegal.com/salary-surveys
-[BCA2018//company//3star]   [best company logo]    [cid:image004.jpg@01D16EF0.38555D60]    [2018 Best Small Companies - small RGB]    [best companies logo 2017]     [cid:image005.png@01D16EF0.38555D60]
-This e-mail is intended only for the addressee named above. As this e-mail may contain confidential or privileged information, if you are not the named addressee, you are not authorised to retain, read, copy or disseminate this message or any part of it. If you are the intended recipient, receipt by you of this e-mail represents your confirmation to agree, or continue to agree, to be bound by our standard Terms and Conditions applicable to the transaction or pending transaction to which this e-mail relates. To request a copy please contact a consultant by e-mail or in writing to the above address.
-BCL Legal is an equal opportunities employer. For further information please visit www.bcllegal.com<http://www.bcllegal.com/> \\ \\
 === JIRA Release Notes ===
 Updated "Forgotten Password" functionality so it now works for users that have a username rather than login with their email address. \\ \\
@@ Line 353: / Line 196: @@
 ===== [IW-809] Current Requirements add to shortlist not working =====
-=== JIRA Description ===
-As a client, when i click on a requirement, go to "Available Candidates" and select a candidate.
-I click on Add to shortlist and i get the following error:
-Procedure: NetClientCandidateSubmit
-<code java>
-IQXWeb ERROR 1:~[FireDAC][Phys][ODBC][Sybase][ODBC Driver][SQL Anywhere]No primary key value for foreign key 'vacancy' in table 'progress'
-</code>
-Inputs:
-<code java>
-pPersonID=XX1206132909200803AC
-pLineID=XX24381511012019002A
-pIsShift=1
-</code> \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 380: / Line 205: @@
 ===== [IW-811] Client Requirements Shortlist not reflecting Shift Progress =====
-=== JIRA Description ===
-NetClientRequirementShortList does not return the list of candidates that are in the shortlist on a shift
-Can this procedure reflect who is shortlisted. \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 392: / Line 212: @@
 ===== [IW-812] Change "Whoops" error messsages =====
-=== JIRA Description ===
-Can you find and replace all "Whoops" error messages with "Error" or something appropriate. \\ \\
 === JIRA Release Notes ===
 Error message wording updated. \\ \\
@@ Line 403: / Line 220: @@
 ===== [IW-815] No error text under NI input field (if NI number is invalid) in Reg Wizard =====
-=== JIRA Description ===
-{{https://iqx-limited.atlassian.net/secure/thumbnail/18843/image-2019-02-12-10-27-06-041.png}}
-As shown above the NI number is not valid, and you are not allowed to continue.  However unlike the other fields there is no red text under the NI input field to tell you that is is not valid. \\ \\
 === JIRA Release Notes ===
 Fixed bug where by error text for NI number input field would not show. \\ \\
@@ Line 415: / Line 228: @@
 ===== [IW-815] No error text under NI input field (if NI number is invalid) in Reg Wizard =====
-=== JIRA Description ===
-{{https://iqx-limited.atlassian.net/secure/thumbnail/18843/image-2019-02-12-10-27-06-041.png}}
-As shown above the NI number is not valid, and you are not allowed to continue.  However unlike the other fields there is no red text under the NI input field to tell you that is is not valid. \\ \\
 === JIRA Release Notes ===
 Fixed bug where by error text for NI number input field would not show. \\ \\
@@ Line 427: / Line 236: @@
 ===== [IW-816] Buttons missing CSS class - client current requirements =====
-=== JIRA Description ===
-In client current requirements if you click on a requirement, click available candidates, and then click on a candidate a model pops up with some buttons on it to let you view the candidate, book or shortlist the candidate.  The buttons have the bootstrap .btn class but no .btn-default or success/info...      classes.  This means that the buttons look greyed out and have no hover effect.
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18852/image-2019-02-13-09-39-02-958.png}} \\ \\
 === JIRA Release Notes ===
 Missing CSS classed added to button in client current requirements. \\ \\
@@ Line 439: / Line 244: @@
 ===== [IW-817] Inconsistencies handling empty table =====
-=== JIRA Description ===
-{{https://iqx-limited.atlassian.net/secure/thumbnail/18854/image-2019-02-13-09-48-26-377.png}}
-In client current requirements, requirement info, current candidates if there is no booked candidates the table is left empty.  If there are no shortlisted candidates a row is added to the shortlisted candidates table which says "No Data".
-If you hover over the text on this row you get a tool tip which says view candidate (which you cant do cause it is not a candidate).
-The tool tip is also partially cut off by the edge of the table.  This means if there was a candidate you would not be able to see the full tool tip letting you know that you can click on their name to view the candidate.
-Remove no data row from shortlisted candidates table if there are no records.  A placeholder could be used with so text prompting them to look at the available candidates tab if they have sufficient rights to shortlist/book a candidate.  e.g.: 'There are no shortlisted candidates for this vacancy/shift - you can add candidates to the shortlist on the "Available Candidates" tab.'
-  {{https://iqx-limited.atlassian.net/secure/thumbnail/18855/screenshot-1.png}}
-Also ensure that the tool tips you get when hovering on table rows are fully visible and not cut off by the edge of the table. \\ \\
 === JIRA Release Notes ===
 Info text added if no results in client current requirements, requirement info, current candidates and available candidates tabs. \\ \\
@@ Line 467: / Line 257: @@
 ===== [IW-818] "Users" icon used twice in tab bar - Client current requirements =====
-=== JIRA Description ===
-{{https://iqx-limited.atlassian.net/secure/thumbnail/18857/image-2019-02-13-10-19-30-335.png}}
-^ current icons in tab bar
-Suggest swapping to font awsome "user-friends" icon for current candidates (as there will likely be less current candidates than available candidates)
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18856/image-2019-02-13-10-20-51-347.png}}
-^ suggested new icons \\ \\
 === JIRA Release Notes ===
 Updated icon on the client current requirements, requirements info, current candidates tab. \\ \\
@@ Line 484: / Line 265: @@
 ===== [IW-819] Candidate details NI Number input always appears editable =====
-=== JIRA Description ===
-On the candidate details page the NI Number field is always 'editable', even if the form is not in edit mode the the other fields are in read only mode.
-Make the NI Number input field read only if the form is not in edit mode (so it behaves like the other input fields) \\ \\
 === JIRA Release Notes ===
 Fixed NI number input component so that it no longer looks editable when it is in read only mode. \\ \\
@@ Line 497: / Line 273: @@
 ===== [IW-821] Different drop down arrow for drop downs =====
-=== JIRA Description ===
-Not sure if this is intended, but as shown below the two different drop down use different arrows to indicate that it is a drop down on the right hand side.
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18861/image-2019-02-13-10-45-38-236.png}}
-Suggest using the same arrow or using an icon such as a plus symbol to show that you can expand the drop down to show more options (and a minus symbol to collapse the drop down when it is in its expanded state). \\ \\
 === JIRA Release Notes ===
 Changed Icon for graded selection and multi select questionnaire component.  + and - symbols are now used to expand and collapse the component. \\ \\
@@ Line 516: / Line 285: @@
 ===== [IW-825] Client Requirements Table/List =====
-=== JIRA Description ===
-As a client, when viewing the client current requirements list, i would like to be able to see the **site details  * and the *clients details** in the table
-Here is how it looks in IQXNet
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18883/IQXNet.png}} \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 538: / Line 301: @@
 ===== [IW-826] Add Client Requirements drop down =====
-=== JIRA Description ===
-As a client, when adding a shift (the shifts dropdown) i would like to be able to see the **clients details  * and the *site details** in the drop down
-Here is how it looks in IQXNet
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18884/IQXNet.png}} \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 555: / Line 312: @@
 ===== [IW-828] Adding row to shifts not clear =====
-=== JIRA Description ===
-When using the "add shift" button in the current requirements it is not clear that you can duplicate/add a row.
-We need to make it more clear!
-Idea for it would be:
-Add a button that says "add row"
-Show a "key" with instructions on how to duplicate a row
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18885/screenshot-1.png}} \\ \\
 === JIRA Release Notes ===
 Icons replaced with text and new add row button added to client current requirements add shifts. \\ \\
@@ Line 574: / Line 320: @@
 ===== [IW-829] Previous Candidates " status " needs to be made more clear =====
-=== JIRA Description ===
-As a client, when using the previous candidates page, We have "temp status" its either "Active" or "<blank>"
-The blanks need to be changed to "Not Available"
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18886/screenshot-1.png}} \\ \\
 === JIRA Release Notes ===
 The status of candidates in the client previous candidates page have been made more clear.  If a candidate is not available it now says "Not Available" instead of being blank. \\ \\
@@ Line 589: / Line 328: @@
 ===== [IW-829] Previous Candidates " status " needs to be made more clear =====
-=== JIRA Description ===
-As a client, when using the previous candidates page, We have "temp status" its either "Active" or "<blank>"
-The blanks need to be changed to "Not Available"
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18886/screenshot-1.png}} \\ \\
 === JIRA Release Notes ===
 The status of candidates in the client previous candidates page have been made more clear.  If a candidate is not available it now says "Not Available" instead of being blank. \\ \\
@@ Line 604: / Line 336: @@
 ===== [IW-830] Previous Candidates info popup =====
-=== JIRA Description ===
-As a client, when using the previous candidates page, if a candidate has worked in multiple places they have a row for each one, this needs changed so its one row per candidate that can be drilled in to.
-Here is how it looks in IQXNet
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18887/IQXNet.png}} \\ \\
 === JIRA Release Notes ===
 Employment history popup added to client previous temps page \\ \\
@@ Line 620: / Line 346: @@
 ===== [IW-831] Previous candidates filter - wording needs changed =====
-=== JIRA Description ===
-On the previouis cnadidates filter screen, the "surname name" needs changed to make more sense
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18888/screenshot-1.png}}
-I suggest "search" or "filter" \\ \\
 === JIRA Release Notes ===
 Fixed wording on the surname filter in client previous candidates. \\ \\
@@ Line 635: / Line 354: @@
 ===== [IW-832] Candidate Adding Availability =====
-=== JIRA Description ===
-The add availability page - there is too much of a gap between the forms
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18890/screenshot-1.png}} \\ \\
 === JIRA Release Notes ===
 Spacing added to time inputs on candidate add availability page. \\ \\
@@ Line 648: / Line 362: @@
 ===== [IW-833] Candidate Availability date picker issue =====
-=== JIRA Description ===
-The date picker on the add candidate availability says "select date/time" this needs changed to "select date" as you are only selecting a date on this field
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18889/screenshot-1.png}} \\ \\
 === JIRA Release Notes ===
 Date picker placeholder text updated. \\ \\
@@ Line 661: / Line 370: @@
 ===== [IW-834] Timesheets row date format =====
-=== JIRA Description ===
-On timesheets, the rows have incorrect dates.
-Current Timesheets
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18891/Current.png}}
-Completed Timesheets
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18892/Completed.png}} \\ \\
 === JIRA Release Notes ===
 Fixed date format on completed timesheets to the UK date format \\ \\
@@ Line 678: / Line 378: @@
 ===== [IW-835] Current Requirements Book Shift =====
-=== JIRA Description ===
-As a client, when on the current requirements, clicking on a requirement, clicking on available candidates and booking a candidate.
-I am then able to book someone else on the same shift, the procedure needs changed to add a check to make sure that noone else is booked into that shift.
-Otherwise show an informational error message to state that they cannot be booked into that shift as someone is already booked into it. \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 692: / Line 385: @@
 ===== [IW-838] Client - Add Contract Requirement - Qty is creating multiple vacancies instead of x inf field Posts. =====
-=== JIRA Description ===
-If I add a Contract Requirement (from a Template)  and in Qty put a number > 1 I get mutltiple vacancies, all with Posts set to 1.
-The Proprocedure may be looping for the count instead of adding the Qty number to the Posts field \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 706: / Line 394: @@
 ===== [IW-839] Review of NetClientRequirmentsList and IW-622 =====
-=== JIRA Description ===
-In preparing the demo it became obvious that the method of distinguishing between Contract and Shift is not standing up to situations where Contract Timesheets can have shifts and a new shift vacancy where no shifts have yet been added - both scenarios lead to showing wrong type.
-In IW-622 I suggested a method of showing based on Temp Desk Type looking at TempDesk.  A similar method would work for the status:
-If tempdesk.desktype = 'S' then 'Shift, else if tempdesk.desktype in ('W','M') then 'Contract'
-A Vacancy has a key join to TempDesk \\ \\
 === JIRA Release Notes ===
 No Release Notes Provided from JIRA \\ \\
@@ Line 722: / Line 402: @@
 ===== [IW-840] Client - Completed TS - not showing column of Temp Name =====
-=== JIRA Description ===
-The other views do
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18903/image-2019-02-19-10-33-41-395.png}}
-But Completed does not.  And if you have several TSs for same week there is nothing to distinguish
- {{https://iqx-limited.atlassian.net/secure/thumbnail/18902/image-2019-02-19-10-35-26-725.png}} \\ \\
 === JIRA Release Notes ===
 Added temp name to the completed timesheets when logged in as a client \\ \\
@@ Line 758: / Line 431: @@
 ==== Iw 801 ====
+\\
+Back to [[releases:iqxweb]]